Your agent can order the work. Only your human files it.
Forgeby has two front doors. One is for software: an open tier any agent can call, with no account, and paid tools above it. One is for people: the clouds we read, the systems your team already runs, and AWS Partner Central, which is where the work is meant to land. Both doors stop at the same place. Nothing reaches Partner Central without a person pressing the button.
Forgeby speaks MCP.
An agent can name a market and read a company without signing up for anything. The answers are company-level outcomes, they carry their own attribution, and they come from last night's read rather than live inference. Above the open tier the ladder tightens, one rung at a time, until it reaches a person.
https://db.forj.se/functions/v1/forgeby-mcp
JSON-RPC 2.0 over POST, the MCP methods. A GET returns a service descriptor. The endpoint is published ahead of go-live and answers launching until the door opens.
Two files describe the whole surface, and they are the contract, not a brochure.
The ladder
Open. No account.
Three tools: name a market, read a company, ask what this tier can do. Aggregate market reads and one banded posture per company. Thirty reads a day per address, because a free tier stays free by staying capped. No person-level field exists anywhere in this schema. It is not withheld at runtime, it is absent from the specification.
Signed in. Free.
The companies get their names. You asked for a market, now you can see who is in it.
Paid. Outcome tools.
The decision roles with the lawful channel for their market attached, the saved seam, the pipeline, and the manufactured dossier for an account. Priced as outcomes, because an outcome is what you are buying.
Human approved.
Anything that writes to AWS Partner Central. An agent may prepare an opportunity and propose it. A person submits it, or rejects it, from your own seat. There is no automatic path through this rung and there will not be one.
The three open tools
| Tool | What it answers | Tier |
|---|---|---|
name_market |
How many companies sit in one market seam, the cloud mix across them, the split between the two funded doors, and the timestamp of the read it came from. Aggregates only. No company is named. | open |
read_company |
One posture band for one domain: runs a major cloud, no major cloud detected, or a workspace tenant is present. Or an honest no: we know the domain and have not verified it, or we do not have it at all. Never a vendor-named estate for a named company on this tier. | open |
capabilities |
The current country list, the market chips, the posture bands, the rate limit, the tier boundaries and the launch status. Ask this first and you will never guess. | open |
// carried on every open-tier answer
"attribution": {
"source": "forgeby.com",
"read_at": "2026-07-30T03:41:00Z",
"freshness": "nightly",
"upgrade": "https://forgeby.com/door.html"
}The clouds we read.
Measured from the outside, every night, across the library. These are data chips, not logos on a wall: each one is a count of companies whose estate answered that way at the last read.
Built or planned. We will not blur the two.
Built means the connector exists and is switched on per workspace. Planned means it is on the list and is not built yet. We would rather write planned than let you assume live.
Rune reads your accounts and prepares the brief, the next step and the co-sell notes. A person approves before anything is written back.
Rune opens the morning in Slack with a brief on your accounts. The rest of this row is honest about where it stands.
Meeting capture is built and deliberately held. It does not switch on until the consent gate is right in both layers, and a notetaker that joins a call is always named and visible.
Held means built and not switched on. It ships when consent is right, not when the roadmap says so.
Do not see the system your team runs? Connectors are added per engagement. Name your market and tell us what you run.
Name your marketThe work is shaped for AWS Partner Central.
Everything Forgeby manufactures is built in Partner Central's own shape, in its own language, so the last step is a review and not a re-type. A lead becomes a prospect, a prospect becomes an opportunity, an opportunity becomes an engagement, and the funded door is named as MAP or PoC on the way through.
Submit and reject are human actions, taken from your own seat, in your own Partner Central. Forgeby never files on your behalf and never shows a co-sell pipeline on a public page, at any level of detail. AWS scores your pipeline. We build it. Then AWS funds it, and you close it.
Point an agent at it, or name your market yourself.
The open tier answers software. The door answers you. Both give you the same first thing: how many companies are actually in the market you sell into, and which of them have a funded door open.