Receipts API emblemTHE RECEIPTS API
A Carter Enterprise LLC company

In agentic commerce, everyone verifies the agent, the buyer, and the payment. Nobody verifies the merchant, or the claim.

The Receipts API checks the business behind the transaction and the claim behind the recommendation, against primary public sources, and returns a dated attestation before your agent buys or recommends anything. Verified as of a date, per a named source. Not a guarantee.

Run a free Know Your Merchant check See how it slots into checkout
Agent identitycovered by agent frameworks and platform auth
Buyer identitycovered by KYC and identity providers
Paymentcovered by card networks, PSPs, and rails
Merchant + claimleft open. This is what we check.
Proof, in their words

The gap is not a theory. The people building these rails say so directly.

Each card below is a receipt: a direct quote or reported finding, with a name and a date attached. No paraphrasing dressed up as a quote.

"...leaves these areas open for the ecosystem to innovate."
Google, AP2 protocol specap2-protocol.org
On merchant and trust verification
"...relies on merchant-provided feeds."
OpenAI / Stripe, Agentic Commerce ProtocolGitHub
Product data is self-reported, not checked
No discussion of seller verification in the protocol design.
Coinbase, x402 protocolcoinbase.com
Payment rail, not a seller check
New FTC policy statement on AI-generated inaccuracy takes effect July 1, 2026.
Federal Trade Commissionftc.gov
Regulatory exposure for unchecked claims
AI answers gave an incorrect business phone number in roughly 36% of cases tested.
Seer Interactive, studyseerinteractive.com
Basic facts, unverified at the source
Reporting on scammers seeding fake support numbers that AI assistants then repeat as fact.
Gizmodo, Dec 10, 2025gizmodo.com
The failure mode, documented
Free tool

The Know Your Merchant check

Enter a business name, a domain, or both. This runs live, in your browser, against free public sources. If a source blocks browser queries, we tell you that plainly and hand you the link to check by hand. We never fake a result.

At least one field is required. We check a global legal entity registry (GLEIF), domain registration records (RDAP), and public Certificate Transparency logs. All three are free and public.
How it slots in

One layer, built for the gap the rails left open

The Receipts API is not a checkout rail and does not compete with one. It produces a portable, machine-readable signal that a checkout rail, an agent, or a crawler can read alongside its own checks.

Emitted as schema.org JSON-LD

Every check returns a ClaimReview-style JSON-LD object: what was checked, what the source said, and when. Any crawler or agent that reads structured data can consume it directly.

Designed to sit alongside AP2 / ACP

Google's AP2 and the OpenAI/Stripe Agentic Commerce Protocol both leave merchant and claim verification open by design. A Receipts API attestation is meant to travel with a checkout payload as an added signal, not to replace either protocol.

Issuable as a W3C Verifiable Credential

For systems that need a signed, portable credential rather than a JSON-LD snippet, the same attestation can be issued as a W3C Verifiable Credential (VC 2.0), tied to the date it was checked.

{ "@context": "https://schema.org", "@type": "ClaimReview", "datePublished": "2026-07-25", "author": { "@type": "Organization", "name": "The Receipts API" }, "claimReviewed": "Public registration and domain signals for \"Acme Supply Co.\" as of 2026-07-25.", "itemReviewed": { "@type": "Organization", "name": "Acme Supply Co." }, "reviewRating": { "@type": "Rating", "ratingValue": "Signals reported, not a score. See detail.", "alternateName": "No trust score is issued." } }
Pricing

An honest ladder, no guarantees attached

Pricing is anchored to the existing Know Your Business (KYB) market, not invented from scratch. No tier here promises a ranking boost, a sales lift, or any other outcome.

Know Your Merchant
Free
The public tool on this page
  • GLEIF, RDAP, and CT lookups
  • Dated result card
  • Copyable receipt (JSON-LD + text)
  • Rate limited, no login
Claim-check API
$0.30 – $2.00 / call
For agents and platforms verifying at transaction time
  • Merchant and claim checks, on demand
  • JSON-LD and VC 2.0 output
  • Priced by source depth and freshness
  • Volume tiers available
AI-Trustable Badge
Monthly
For merchants who want a standing, re-checked badge
  • Recurring re-verification
  • Badge markup for merchant sites
  • Priced by merchant volume, contact for a quote
  • No ranking or placement promises
Enterprise
Custom
For platforms, marketplaces, and agent builders
  • Volume claim-checks
  • SLA and dedicated support
  • Custom source integrations
  • Contact us to scope
Anchoring, for reference: Stripe Identity verification runs around $1.50 per verification; Sumsub's published KYB range runs roughly $1.35 to $1.85 per check. The Receipts API's claim-check pricing is set relative to that existing market, not to a target margin. No tier guarantees rankings, revenue, or any other business outcome.
FAQ

Plain answers

What does The Receipts API actually verify?

It checks a named merchant or business against free, primary public sources, a global legal entity registry (GLEIF), domain registration records (RDAP), and Certificate Transparency logs, then reports what those sources say, dated and linked. It does not verify agents, buyers, or payments, those are already covered elsewhere.

Is this a trust score or a guarantee?

No. We never issue a numeric trust score and never guarantee a merchant or claim is legitimate. We report only what named public sources returned, as of a specific date, with a link back to each one.

Why isn't this already handled by agent checkout protocols?

Google's AP2 spec leaves merchant and claim verification open for the ecosystem. The OpenAI/Stripe Agentic Commerce Protocol relies on merchant-provided feeds. Coinbase's x402 does not address seller verification. That is the gap this fills.

What format is an attestation issued in?

As schema.org JSON-LD (ClaimReview) that an agent or crawler can read directly, and optionally as a W3C Verifiable Credential (VC 2.0) for systems that need a signed, portable credential.

Is this legal or financial advice?

No. This is an educational and informational verification tool. It is not legal, financial, or investment advice, and it does not guarantee rankings, revenue, or outcomes for any merchant.