// cli v0.5.6 · live in production

Nitrograph is the
agent commerce
platform.

Agents are becoming users of your software. Nitrograph is how you let them in, control what they do, and charge for it.

Book a pilot →$ npx nitrograph →Read the docs →

live · Agent Checkout pilot18,000+ services indexedx402 · liveMPP · liveTAP · soon

Checkout/ package · approve · meter

18,000+/ services · discovery funnel

reputation/ cross-merchant agent memory

agent session · claude-4-opus → nitrograph

LIVE

try:

// type an intent above, press run, watch the live pipeline

// calls hit api.nitrograph.com · no keys · real catalog data

live · idle

§ 01 / Agent Checkout

Let agents use your software and charge for the work they run.

Agent Checkout is the product merchants buy: package valuable workflows, let customers approve agents, meter only successful action runs, and reconcile the result as revenue.

Book a pilot →See merchant demo →

01 / package

Package actions with your pricing model.

Credits, workflow packs, per-action pricing, or account add-ons. You decide what agent work is worth.

02 / approve

Let customers control which agents act.

Customer admins approve agents, set caps, review usage, and revoke access without sharing broad API keys.

03 / cart

Meter only successful billable actions.

Agents open carts, run actions, add line items, and close billing evidence. Blocked or failed work does not bill.

04 / settle

Turn approved usage into merchant revenue.

Nitrograph produces the ledger, webhook, invoice reference, and payout trail your finance team can reconcile.

§ 02 / the money loop

Make the moment an agent creates revenue visible.

Customer approves

A billing owner approves an agent, allowed actions, and a spend cap.

Agent opens cart

The cart is scoped to one merchant, workspace, grant, and credit balance.

Actions run

Free, metered, blocked, failed, and replayed actions all hit the same ledger.

Success bills

Only successful billable line items debit credits and create revenue.

Cart closes

Credits are debited, idempotency is locked, and the period is ready to close.

Merchant gets paid

The merchant keeps the transaction revenue; Nitrograph keeps the commerce margin.

Evidence drops out

Finance gets usage export, invoice reference, webhook delivery, and audit trail.

cart.close()settled

line itemmeterbill

search_accountsfree_success$0

enrich_contactmetered_success$500

export_full_segmentblocked$0

credits debited5

merchant revenue$490

Nitrograph margin$10

webhook.billing_period.closed delivered in 283ms

§ 03 / why nitrograph

The moat is cross-merchant
agent reputation.

// 01

You only see your own agent traffic.

Any SaaS team can meter its own agents. Only Nitrograph sees behavior across many merchants, rails, actions, approvals, and billing outcomes.

↳ one merchant → partial signal

// 02

Reputation travels with the agent.

When an agent reaches your software, you should know whether it pays reliably, respects caps, retries safely, and avoids abusive patterns.

↳ cross-merchant → trust memory

// 03

That is hard to build alone.

The more merchants meter through Nitrograph, the better the agent reputation graph becomes, and the safer every merchant launch gets.

↳ network effect → checkout moat

§ 04 / Discovery

Discovery is the funnel that
brings agents to merchants.

// Keep the index. Demote it to the demand path: get listed, get found, get billed.

LIVE · DISCOVERY

Agents find the right merchant workflow.

18,000+ services ranked by relevance, trust, operational memory, and payment rail. Discovery gets agents to the merchant surface where Checkout can meter the work.

nitrograph_discover("b2b research + enrichment")

01apollo0.94MPP

02x402-lead-enrichment-api0.91x402

03tavily0.88MPP

04x402-web3-job-market-api0.84x402

05parallel0.81MPP

LIVE · SERVICE MAPS

The map lowers agent integration failure.

We run a probe fleet against every service in the catalog. Version drift, schema quirks, undocumented caps, param combinations that silently return empty. A better map means more successful billable actions.

#07b9apollo · responses wrapped in { success, data } · top-level reads undefined

#653dapollo bulk cap is 100 records per call · 400 over cap

#50cdapollo uses organization_id (singular), not organization_ids

#5593apollo · q_organization_keyword_tags wants tag IDs, not free text

LIVE · MCP-NATIVE

The agent-native path into Checkout.

One install. Four tools. Every MCP-compatible client (Claude, Cursor, Cline, Zed) gets discovery, service maps, outcome reporting, and pattern reporting as first-class tool calls. The developer funnel stays live; the merchant funnel gets paid.

1$ npx nitrograph · installedok

2nitrograph_discoverlive

3nitrograph_service_detaillive

4nitrograph_report_outcomelive

5nitrograph_report_patternlive

// privacy by design

Your traffic never enters the graph.

Nitrograph is not a proxy. We process the discovery queries, task context, outcome diagnoses, and workflow reports your agent sends to Nitrograph. We do not automatically see the downstream payload sent to the selected service or the service's response.

Operational memory comes from our own probe fleet. We run structured tests against every service in the catalog, and agents can report integration outcomes. Aggregated reports become gotchas and proven patterns so the next agent avoids the same failure.

/ graph stores

service_id
endpoint_path
probe_result
latency_ms
discovery_query
outcome_diagnosis
workflow_steps
rail
version_hash

/ graph never stores

your_prompts
your_api_keys
your_user_data
downstream_payloads
service_responses
private_keys

§ 06 / agent readiness

Is your software ready to bill agents?

Agent Checkout turns your product's agent surface from readable and callable into billable. The gap is not just API access. It is package rules, customer approval, metering, caps, revocation, and proof finance can trust.

Your website is for humans. Your docs are for developers. Your agent surface is for autonomous software buyers, operators, and customer-approved agents acting inside existing accounts with explicit spend authority.

Book a pilot →Agent readiness →

headless inquiryagent review

$ POST /v1/headless/inquiries

RETRIEVE

+ website

+ docs / API reference

MAP

→ workflows, approvals, schemas, usage, trust

RECOMMEND

→ merchant path, audit, sprint, or monitoring

// 01

Billable

Package rules, customer approval, credit debits, billing evidence, and revocation make agent work commercially safe.

// 02

Readable

Make your product understandable to agents: services, workflows, schemas, permissions, and constraints.

// 03

Callable

Expose the workflows customers want agents to run through APIs, MCP, service catalogs, and call cards.

§ 07 / rails

Payment rails are the plumbing,
not the pitch.

// Two rails live today. More as they ship.

LIVE

x402

// native HTTP stablecoin payments

USDC on Base, Polygon, and Solana. Coinbase co-founded, open standard. Pay-per-call with receipts on-chain. 18,000+ services in the catalog.

// Catalog surfaces every x402 service's payment contract
GET /v1/service/x402-lead-enrichment-api
  rail: "x402"
  cost: { amount: "0.001", currency: "USD" }
// agent calls the service → handles its 402 → pays → 200 OK

LIVE

MPP

// Machine Payments Protocol

Session-based streaming payments on Tempo. Sub-second settlement, delegated spend authority, no per-call signing. Co-designed by Stripe and Tempo. 90 services in the catalog.

// Catalog exposes every MPP service's session endpoint
GET /v1/service/apollo
  rail: "mpp"
  cost: { amount: "0.0056", currency: "USDC" }
// agent opens session with service → streams calls → settles

PHASE 2

TAP

// Trusted Agent Protocol

Identity-bound agent transactions with reputation carry-over. For services that require a known caller, not just a funded one.

// coming when spec stabilizes
agent = nitro.tap.whoami()
agent.rep.score → 0.94 · 12,403 tx

PHASE 2

A2A

// agent-to-agent settlement

Agents paying agents directly. Nitrograph routes intent to the best counterparty, not just the best API.

// route intent → human-or-agent service
nitro.route({ intent: "legal-review" })
↳ matched agent://firm.delacroix/contracts

§ 08 / integration surfaces

Built on HTTP. Works with
every agent framework.

LIVE

Hosted MCP

https://api.nitrograph.com/mcp

LIVE

REST API

POST /v1/discoverGET /v1/service/:slug

LIVE

Local MCP (stdio)

npx nitrograph

LIVE

Agent Harness

npm i nitrograph

PHASE 3+

Framework adapters

langchain · crewai · vercel-ai · mastra · pydantic-ai

View the full API reference →

§ 09 / pilot pricing

Turn API calls into billable agent actions.

// measured billing

Price usage when agents create value.

Your API suite becomes an agent commerce surface: package the endpoints customers want automated, attach credits or per-action prices, and meter only approved successful calls. Nitrograph supplies the customer controls, usage ledger, and billing evidence; you keep the merchant relationship and pay through transaction margin.

Request a Pilot

packageAPI suites

Wrap the endpoints agents need as priced actions, workflow packs, or credit-backed products.

metersuccessful work

Approved calls that complete create billable line items. Failed, denied, or out-of-scope requests stay visible at $0.

reconcilebilling evidence

Close each cart with customer, grant, action, credits, and invoice references finance can audit.

Turn agent usage into merchant revenue.

Book a pilot →$ npx nitrograph →// agents still enter through discovery · merchant funnel first

Let agents use your software and charge for the work they run.

Package actions with your pricing model.

Let customers control which agents act.

Meter only successful billable actions.

Turn approved usage into merchant revenue.

Make the moment an agent creates revenue visible.

Customer approves

Agent opens cart

Actions run

Success bills

Cart closes

Merchant gets paid

Evidence drops out

The moat is cross-merchant agent reputation.

You only see your own agent traffic.

Reputation travels with the agent.

That is hard to build alone.

Discovery is the funnel that brings agents to merchants.

Agents find the right merchant workflow.

The map lowers agent integration failure.

The agent-native path into Checkout.

Your traffic never enters the graph.

/ graph stores

/ graph never stores

Is your software ready to bill agents?

Billable

Readable

Callable

Payment rails are the plumbing, not the pitch.

x402

MPP

TAP

A2A

Built on HTTP. Works with every agent framework.

Hosted MCP

REST API

Local MCP (stdio)

Agent Harness

Framework adapters

Turn API calls into billable agent actions.

Price usage when agents create value.

Turn agent usage into merchant revenue.

The moat is cross-merchant
agent reputation.

Discovery is the funnel that
brings agents to merchants.

Payment rails are the plumbing,
not the pitch.

Built on HTTP. Works with
every agent framework.