Intra

Agent route contract

Businesses publish a capability. Agents handle the protocol.

Intra creates a managed route from a business's plain-language service details. Merchants never need to build or host MCP infrastructure themselves.

Capability

A single service with clear inputs, outputs, and a current operational status.

Payment boundary

A Celo x402 fee can pay for fresh information. It is not an order payment.

Control boundary

Routes can pause. Final orders always need human approval.

Generated capability manifest

Illustrative contract only. This is not a live merchant endpoint or a settlement claim.

{
  "version": "0.1",
  "business": "campus-print-hub",
  "capability": "flyer-printing-quote",
  "endpoint": "/v1/campus-print-hub/flyer-printing/quote",
  "status": "ACTIVE",
  "input_schema": ["size", "quantity", "colour", "deadline", "deliveryArea"],
  "returns": ["quote", "valid_until", "turnaround", "availability"],
  "query_payment": { "protocol": "x402", "network": "eip155:42220", "asset": "USDC", "max_fee_usd": 0.05 },
  "final_order": { "approval_required": true, "channel": "whatsapp" }
}

Agent lifecycle

  1. 01

    Discover an active route

    Agent reads the capability, freshness timestamp, supported inputs, and order-approval policy.

  2. 02

    Validate the buyer brief

    The agent sends only the required structured fields. A paused or stale route rejects the request before any payment is requested.

  3. 03

    Pay only when enabled

    The route returns HTTP 402. The agent retries with a signed X-PAYMENT authorisation; a server-side call to the official Celo facilitator verifies it and settles on-chain. Until the facilitator key is configured, Intra returns an explicit unavailable state.

  4. 04

    Receive a time-bound quote

    The result contains price, currency, availability, turnaround, assumptions, expiry, and merchant contact channel.

  5. 05

    Hand the final order to a human

    Intra prepares the WhatsApp message. The buyer reviews, sends, and pays any final order directly.

Payment status

The capability API, quote workflow, and the Celo x402 payment adapter are implemented and tested. Live settlement activates when the official facilitator API key is set in the server environment; until then a paid route returns an explicit unavailable state. No screenshot, preview, or database row is ever treated as a payment receipt — only a facilitator-verified transaction hash.