This is the canonical entry path for agents and builders: discover PacketOps and DiligenceOps, quote a run, receive a payment challenge, start the rail, check status, fetch the return package, and record the receipt.
Agents do not need to decode the site. They choose a rail, pass the required context, attach payment or payment reference, and receive a package target.
Best for document packets, onboarding sets, submission folders, and missing-item checks.
Pricing: entry 49, standard 99, pro 249 USD units.
Returns: manifest, missing-item report, readiness object, exception object, attestation.
Read PacketOps routeBest for vendor evidence, diligence folders, readiness scoring, and review package preparation.
Pricing: entry 99, standard 199, pro 399 USD units.
Returns: evidence inventory, missing-item report, risk summary, readiness score, attestation.
Read DiligenceOps routeThe sequence uses exact routes, stable fields, status URLs, package IDs, receipt IDs, and verification fields.
GET /api/agent-use returns rails, modes, pricing references, and schemas.
mode=quote_run returns amount, currency, package level, and accepted payment methods.
mode=create_payment_challenge returns a 402-style JSON envelope with amount, run ID, expiry, and accepted methods.
mode=start_agent_run requires rail key, idempotency key, and a payment or wallet reference.
mode=get_run_status or GET /api/agent-use?run_id=... returns the current run state.
mode=fetch_return_package returns the package contract and proof fields.
mode=record_agent_use_receipt binds receipt ID, payment reference, return package ID, and hash.
The payment challenge is intentionally portable. It can point to hosted checkout, wallet allowance, invoice reference, stablecoin reference, x402 reference, or AP2-style mandate reference.
{
"payment_required": true,
"challenge_id": "payment_challenge_...",
"rail_key": "packetops",
"amount_units": 99,
"currency": "usd",
"accepted_methods": ["hosted_checkout", "agent_allowance", "payment_reference", "invoice_reference", "stablecoin_reference", "x402_reference", "ap2_mandate_reference"],
"status_url": "/api/agent-use?run_id=...",
"receipt_required": true
}For production runs, attach a payment or wallet reference. For sandbox runs, send the same shape and keep the receipt trail intact.
Agents call quote_run, /api/agent-use, /api/agent-pricing, or MCP get_movement_fee_schedule. Tool access and wallet opening return 0 units. Completed rail movement carries transaction or escrow movement fees.
Applied to completed transaction movement. Minimum 0.01 units.
Applied to escrow release after validation. Minimum 0.05 units.
Applied when both transaction movement and escrow release are used.