The site, the portal and the docs

Every product launches with a landing site that sells it, a developer portal that runs each account, and docs that teach it. They come from the file, under your brand, and never drift from it.

One file, three productsCopy Anchor Link

Each is specified as a product of its own, with its parts, paths and quality bar. Seven rules hold for all three.

Site tests, tickets and campaigns run outside the product, on these Events.

The landing siteCopy Anchor Link

The landing site sells the product to a person who has never called it. An agent that asks / for JSON gets the root JSON: the name, the Verbs and the other registers.

Paths.

1. A person asks a search or answer engine, lands on a Noun page, and sees a real answer with its price.
2. They press Try it, and the page mints a Test key and runs the call.
3. They read the price page and the refund rule, sign up, pay through Checkout, and leave with a Live key in the portal.
4. A finance lead reads the offer card and terms, then adds the seller to their agents' allowed sellers.

States. The site serves the live Version, and each superseded Version's terms stay readable at their own URL. Status shows each Interface as up, degraded or down, and each incident as open or resolved.

Quality bar. The price is on the first screen, and every example on the page runs. Every page reads with no script, holds AA contrast, and fits a phone's width.

The developer portalCopy Anchor Link

The developer portal runs each account after sign-up, at /dashboard.

It serves two kinds of account. A Customer buys; a supplier, in a Marketplace or a Service API, sells through the product and is paid by it.

Paths.

1. A Customer signs in, takes a Test key, and makes a first call from the docs.
2. They buy credits through Checkout, and a Live key appears.
3. They set a spend ceiling, invite a member, and give one agent a mandate with a 200 USD budget.
4. They replay a failed webhook delivery, see why a run waits, or dispute a charge with its receipt.
5. A supplier applies, passes identity and tax checks, finishes payout onboarding on Stripe, publishes items, and sees a first payout.

States.

Quality bar. An empty screen says why it is empty and what fills it, and every refusal shows its cure. An export holds every record, Event and receipt the account owns.

A supplier fills orders over the API, CLI or MCP, or in a delivery app built on the UI contracts. The portal runs the supplier's account, not the work.

The docsCopy Anchor Link

The docs, at /docs, teach a person and an agent to make the first paid call, then every call after it.

Paths.

1. A developer opens their language's quickstart and copies a call with their Test key in it.
2. The call answers 200, and the reply's X-Cost matches the price on the page.
3. A later call answers 402; its type link opens the error page, whose cure is one Checkout link.
4. An agent reads llms.txt, then a Verb's Markdown twin, and calls it with no page rendered.

States. Each page set follows its Version: live, superseded or deprecated with a link to the migration guide, then retired and still readable.

Quality bar. Every printed call runs against the Test twin. A Verb's page exists from the deploy that adds the Verb.

Contracts and an exampleCopy Anchor Link

ExampleCopy Anchor Link

companyfacts with its brand, one page of its own on the site, and one guide in the docs.

import { define, secret } from 'apis.dev'

/** Any company by its domain, with its headcount and sector. */
export default define({
  name: 'companyfacts', domain: 'companyfacts.apis.dev',
  …
  brand: { logo: './logo.svg', color: '#0b6e4f' },        // every face, email and receipt
  site: { pages: { '/coverage': './coverage.mdx' } },     // your page; the rest stays generated
  docs: { guides: ['./guides/enrich-a-crm.mdx'] },        // checked against the file at each deploy
  sources: {
    firms: { origin: 'https://firms.example.com', key: secret('FIRMS_KEY') },
  },
  Company: {
    domain:    { type: 'url!#',   from: 'firms', map: 'website' },
    employees: { type: 'number?', from: 'firms', map: 'headcount' },
    sector:    { type: 'string?', from: 'firms', map: 'industry' },
  },
  offer: { 'Company.get': 0.002, 'Company.search': 0.005 },
})

Three products from one file, so the page that sells a Verb, the screen that bills it and the page that teaches it always agree.