pitch.apis.credit

apis.credit

Agents can't grant credit. They can pull the file.

Business credit and KYB, UCC-9 lien intelligence, and prequal simulation: per call, at flat prices posted on a public rate card. Same key as apis.finance, same catalog, same rate card.

↓ scroll · arrow keys

Credit data is sold the way agents can't buy

You can ship an Agent that prices a Borrower before lunch. Buying the data to do it takes an annual contract, a sales call, seat pricing, audit rights over your usage, and a minimum your product hasn't earned yet.

That model assumed the reader of the price was a procurement team. Increasingly the reader is a machine: an origination system, a servicing stack, an Agent acting for either. A machine cannot sit through procurement, and a price it cannot read at call time does not exist for it. So the builders shipping agents either go without the file, or inherit an enterprise contract shaped for a company they are not yet.

apis.credit is the counter-shape, term by term: every SKU flat, fixed at post, listed on a public machine-readable rate card, metered per call, released only on the served record.

The catalog: posted, per call

skureturnspricestatus
Business credit · KYBentity verification, registrations, lien and judgment flags, cash-flow signals on a Borrower$3.00 per file pullLIVE
UCC-9 lien intelligencedebtor search across state filing offices: lien positions, secured parties, filing images (state office fees pass through at cost)$4.00 per searchLIVE
Prequal simulationa Lender's published criteria run against a Borrower file: a typed WOULD_MEET or WOULD_NOT_MEET per criterion$0.01 per calculation, metered as amortization math on the shared cardLIVE
KYA agent scorescounterparty score for an Agent: Mandate history, settlement record, delegation chainposts with the SKUROADMAP · spec posted

This table is a view of the family's one rate card, never a second price list. If a price isn't posted, the SKU isn't live, and the row says so. Every fee here is a Telemetry Fee: pure data, named on the receipt, never a percentage of any credit. The family's honest-liveness law binds these stamps: a LIVE stamp is verified against reality on publish day, and anything unverified flips to ROADMAP with no other copy change.

Postedapis.finance/rate-card.json

The family rate card is served, machine-readable, at apis.finance/rate-card.json. The prices above are quoted from it, byte for byte where they overlap.

Postedapis.credit/llms.txt

The stamps above are the door's own: llms.txt carries the same SKUs and statuses as this table, stamp for stamp.

The record carries its own regime

The use restriction is not a paragraph in a PDF you agreed to once. It is a term of every call, typed into every response as a permitted_use object on the record itself:

// SPECIMEN · the shape as published on the door itself
{
  "object": "credit.business_file",
  "specimen": true,
  "subject_party": "SPECIMEN MOTORS LLC (Borrower)",
  "permitted_use": {
    "regime": "COMMERCIAL",
    "fcra_consumer_report": false,
    "restriction": "Commercial credit, KYB, and simulation use only. No consumer purpose. This restriction is a term of the call.",
    "terms": "https://apis.credit/use-restriction"
  },
  "entity": { "legal_name": "SPECIMEN MOTORS LLC", "status": "ACTIVE", "registry": "TX SOS" }
}

apis.credit is not a consumer reporting agency as defined by the Fair Credit Reporting Act, and nothing served from this door is a consumer report. The SKUs are commercial: business credit on entities, KYB, lien intelligence from public filing offices, simulation arithmetic. A request declared for a consumer purpose does not return a thinner file: it returns a typed BLOCKED, and nothing is metered, because a refusal is not a product.

Postedapis.credit

The specimen above is the shape published on the live door, stamped SPECIMEN there as it is here: the compliance posture is a rendered artifact on the page, written to be forwarded.

A Simulation is not a Decision

The line this door holds is the family's structural fact: the Lender-Reserved acts (extend credit, take the Application, negotiate terms, decide) are performed by a licensed Lender alone, never by software and never by a pool. This door sells none of them, and a call that asks for one returns a typed BLOCKED with the statute, the party, and the route.

That is what makes the prequal SKU safe to sell. A Simulation runs a Lender's published criteria against a Borrower file and returns a typed WOULD_MEET or WOULD_NOT_MEET per criterion, with the criterion named and the input echoed. It opens no Application, starts no clock, attaches no Reg B duty, and produces no Decision. The Lender publishes the criteria; the platform never authors them, never scores against unpublished ones, and never ranks Lenders by the result. What is sold is arithmetic against posted criteria, metered as data on the served record.

The restriction is the feature: because nothing here decides, everything here can be priced, posted, and called by an Agent without a procurement cycle.

The agent is a reader

The machine doors are the docs, linked in the head and the footer of the live page, with the rate card linked again in the first view:

  • /llms.txt · the door described for machine readers: SKUs, prices, regime, family map.
  • rate-card.json · the family's one card, served from the hub; this door links it, never mirrors it.
  • /mcp and /.well-known/x402 · typed, not silent: each returns a typed ROADMAP object naming its route and the card, because a dead end is a conformance failure and a typed status is the product behaving.
Postedapis.credit/llms.txt

llms.txt is live on the door and states the same SKUs, prices, statuses, and FCRA posture as the page, so a crawler and a compliance lead read the same facts.

Postedapis.credit/.well-known/x402

The not-yet-live settlement door says so in type: /.well-known/x402 serves a typed ROADMAP object today, carrying the rate-card URL and a contact route.

Postedapis.credit/mcp

The same holds for the agent door: /mcp serves a typed ROADMAP object today, naming the hub as where the family MCP server posts, with the rate-card URL and a contact route.

Pendinggate: x402 settlement live on the family and the discovery object flips from ROADMAP

Stated plainly: prices are posted and machine-readable now; x402 metering itself posts when settlement is live. Until that flip, keys and calls run through the intake at keys@apis.finance, and no surface in this record implies otherwise.

One family, one key, one motion

The motion is B2A: the Agent is the caller and the flagship Consumer Pattern of the family. The builder who ships the Agent holds the key and evaluates this door the way agents do, by reading its machine surfaces; a human working through an agent surface (B2H2A) rides the same door unchanged. One ICP, one motion: the builder arriving data-first. The dealer principal, the desk, and the origination buyer each have their own door elsewhere in the estate, and this deck does not pitch them.

substrate — apis.finance

apis.finance

the hub

the Agent Money Kernel and the family catalog: one key, one rate card · LIVE

apis.credit

you are here

the data door

business credit · KYB · UCC-9 lien intelligence · prequal simulation · LIVE

apis.loans

the origination door

stands at its own address, never an alias · ROADMAP

apis.mortgage

the entity-gated register

WAITLIST · never redirects into the hub: the licensing boundary starts at the URL

The grammar is fixed estate-wide: api.X is one API for one profession; apis.X is a family of APIs sharing one key. The plural is this family's name on every surface, snippet, and mailbox.

Where it stands

Postedapis.credit

The door is live at apis.credit: hero, SKU table with statuses, the specimen record with its permitted_use object, the compliance posture written to be forwarded, and the key-request intake. Honest pre-launch surfaces are typed, not hidden.

Postedapis.finance

The hub is live at apis.finance, and its page links the family rate card, its llms.txt, and this door by name as ordinary links.

Pendinggate: first metered call by an external Agent settles against the posted card, receipt in evidence

No usage, volume, or revenue is claimed anywhere in this record, because none is posted. The claim that matters is a third party's Agent pulling a record at the posted price and the receipt naming the Telemetry Fee; it posts when it has happened.

Pendinggate: KYA price posts on the family rate card with the SKU flipped to LIVE

KYA agent scores are ROADMAP with the spec posted. The row ships when its price does, and not before, because a Telemetry Fee never sits on a row whose status is not LIVE.

Request a key

The front door is apis.credit · it serves today.

If this was forwarded to you: apis.credit is the data door of the apis.finance family, where credit intelligence is sold the way agents buy it: business credit and KYB, UCC-9 lien intelligence, and prequal simulation, per call at flat posted prices, with the use restriction typed into every response and the acts the law reserves left unsold. Every claim above carries its own state and evidence. If you ship agents that need the file: request a key. If you know who does: forward this.