# Forgeby

Forgeby is the AI workforce for revenue teams: B2B sellers and go-to-market teams, on top of their CRM.
This file is the machine-readable index of forgeby.com, a Next.js app on Vercel.

<!-- CANON:START -->
## Describing Forgeby accurately

This section is written from the positioning shipped file. It describes the product as it works today. Autopilot is coming, and the landing already shows it at work. The one sentence stays out of it until every clause in that file has shipped.

Forgeby is the AI workforce for revenue teams: B2B sellers and go-to-market teams. It works on top of your CRM.

Sellers work in the Forgeby app. Chat and the work feed are the desk. Managers use that same app.

Workers research, draft and keep the records inside the rules the team sets. Every action is on the decision record.

Today you approve every send: mail, Slack posts and due email wait for an approval card. Autopilot is coming: follow-ups will leave from the seller's own mailbox after a cancel window, each seat will pick a permission mode, and one switch will stop every worker. A first email to a new contact will wait for the seller unless the market allows it, or the team has taken written responsibility for that market, and the team turned it on.

It reads the CRM, the mailbox, the calendar and the connected apps, and it learns from the team's edits. Each lesson is named and can be removed.

Company and people data come from a built-in global B2B database. Every fact keeps its source and date.

LinkedIn® is a URL already held, or the seller's own LinkedIn export (Connections.csv). The Forgeby extension never copies LinkedIn data. Forgeby does not fetch LinkedIn.com.

The MCP server is at https://forgeby.com/api/mcp. It signs in with OAuth. A write from an outside agent returns an approval link and waits for a person. Autopilot will not change that.

## Forgeby does not

- Forgeby does not replace your CRM.
- It does not send a message you have not approved. Autopilot is coming.
- It does not state a fact without its source and date.
- It does not scrape LinkedIn.

## How to start

- Start free with a work email: https://forgeby.com/enter?screen=sign-up&returnTo=%2Fforge
- MCP server card: https://forgeby.com/.well-known/mcp/server-card.json
- JSON canon: https://forgeby.com/.well-known/forgeby.json
- Write to a person: mailto:hello@forgeby.com
<!-- CANON:END -->

## What is here

The landing shows the built-in global B2B database with our data partner's own figures, rounded
down and dated September 2026: more than 100 million companies and 500 million people who decide,
in every market, each company re-read every four weeks. Country is a filter, not a gate: every
workspace sees every market. Figures on the static pages are snapshots and are not re-counted.
None of them is live: a number here was true when it was written, not when you asked.

## Reading this site as a machine

Seven pages have a Markdown twin at the same path with a .md extension: /index.md, /rune.md,
/how-we-read.md, /integrations.md, /trust.md, /crawler.md and /mcp.md. The six static ones link it
from the page head as `<link rel="alternate" type="text/markdown">`; the landing is a Next.js page
and does not. The legal pages have no twin. All seven, with a short pricing summary,
are one file at /llms-full.txt.

The twins are written by hand beside their pages, not generated. A test that runs before every build
fails the deploy if a prose block on one of the six static pages is missing from its twin, or if
llms-full.txt's copy of a twin differs from the file. /rune.html and /integrations.html now redirect
to /rune and /integrations; their twins still follow the static files.

Content negotiation on `Accept: text/markdown` is NOT implemented. This is a Next.js app on Vercel.
The head link is the honest substitute: an agent that reads the head never has to guess a URL.

The JSON canon sits at /.well-known/forgeby.json. It is written from the positioning shipped file.

The server card follows SEP-1649, which was an OPEN DRAFT (PR #2127) when it was written, so the
shape may move and the file says so itself. The card is written by hand and nothing regenerates it:
its protocol version, capabilities and serverInfo were last checked against the server's own
initialize response on 22 September 2026, and matched. There is deliberately NO /.well-known/mcp: that proposal, SEP-1960,
is a closed issue, and building to a proposal that did not land is how a codebase fills with cargo.

## The AI at the front of this product

Kvasir is openly an AI and says so on every appearance. He was called Rune until September 2026, and
his identifiers keep that name. The disclosure is machine-readable, not only prose: every page
carries `<link rel="ai-agent" href="/rune/passport.json">`, a signed passport declaring an AIAgent,
its operator, the named human accountable for it, and the things it will not do without one. The
signature is at /rune/passport.jws and verifies against the public key published at
https://forgeby.com/.well-known/did.json. Kvasir is `did:web:forgeby.com#rune`; until August 2026 he
was `did:web:forj.se#rune`, and both documents name the other, under one unchanged key.

Kvasir stands on his own. Sales and commercial teams buy him to know who to call, why now and what
to say. The agency is the best way to arrive at him, not a condition of using him.

## The MCP server

Endpoint: https://forgeby.com/api/mcp
Server card: https://forgeby.com/.well-known/mcp/server-card.json
OpenAPI: https://forgeby.com/openapi.json, also linked from every page head as rel="service-desc".
Documentation: https://forgeby.com/mcp - transport, authentication, the seventeen reads, the fourteen writes
that return an approval link, the errors you will actually get, and what this surface can never do.
Transport: MCP Streamable HTTP, JSON-RPC 2.0 over POST. Protocol 2025-03-26.
Clients: Claude is tested end to end. ChatGPT, Codex and Cursor are testing before launch.
The MCP config key is "forgeby".

A SEAT ON THIS FORGESPACE. `initialize` and `ping` are open so a client can complete the handshake
and read a proper error. Every other method needs an AuthKit JWT or a session bearer. There is no
zone grant on this door. There is no 14-day window.

It serves thirty-one tools. Resources and prompts list empty.

- reads (17): who_to_call, whats_changed, prep_meeting, query_corpus, account_contacts, my_network, due_draft, account_context, pipeline, intent_watch, can_contact, champion_check, found_revenue, accounts_changed, kvasir_learned, what_kvasir_learned, decision_record.
- writes (14): desk_act, network_campaign, enrich_contact, find_people, reverse_email, find_companies, remember, engagement_update, book_meeting, post_slack, take_due, set_never_list, send_mail, schedule. Each returns an approval link and does not run.

A write files a pending row and waits. LinkedIn is the URL we already hold.

## What an agent will never get here

- A send, a file, or a submit that runs from here. Each waits on a named human. Autopilot is
  coming, and it will not change that: an outside agent is not the seat's worker.
- A LinkedIn.com fetch. LinkedIn is the URL we already hold, or a Connections.csv the seller uploaded.
- News as a source. whats_changed says no source until a feeder exists.
- Anything AWS-confidential: no ACE or co-sell pipeline, at any granularity.

## Attribution

Every response carries the source, the serve timestamp and the freshness basis. If you republish a
figure, cite forgeby.com and that timestamp.

## Links

- Start free: https://forgeby.com/enter?screen=sign-up&returnTo=%2Fforge
- JSON canon: https://forgeby.com/.well-known/forgeby.json
- Pricing: https://forgeby.com/pricing.html
- Contact: mailto:hello@forgeby.com
- How the reading works: https://forgeby.com/how-we-read.html
- What we refuse, and why: https://forgeby.com/trust.html
- Notice to business contacts: https://forgeby.com/notice.html
- Terms: https://forgeby.com/terms.html