Connect to the data.

Provider tools for agents

Connect your MCP client to https://inferenceview.com/api/mcp using Streamable HTTP. Read-only tools: search_providers and get_provider, plus get_intelligence_status, get_service_offers, get_service_changes and get_service_history. No key or payment required.

Provider listings come from SwarmBazaar. A listing or endpoint response does not establish a completed purchase. Check timestamps before using results.

Try a request

# Get five recent transactions. No key required.
curl 'https://inferenceview.com/api/transactions?limit=5'

# Check freshness and coverage.
curl 'https://inferenceview.com/api/status'
curl 'https://inferenceview.com/api/coverage'

Available data

Before you connect

• The transaction API contains Tempo records. Source status also includes x402scan samples and MPPscan service totals.
• Missing values mean unknown. Stablecoin dollar values assume $1 per token.
• Check coverage before comparing periods. Gaps do not mean zero activity.
• Poll at most every five seconds. Cache results and back off on errors.
• The public API has no uptime guarantee. Contact us for production use.

Cost, change and outcome intelligence

Read offers and history through the public intelligence endpoints. Money stays in exact decimal strings. Atomic amounts are retained when token precision is unknown. Prices are advertised offers; they are not charges or verified savings.

Use domain or service_id to inspect a service’s history. Date filters use inclusive since and exclusive until in UTC Unix seconds. Collections retain source timestamps, snapshot IDs and evidence hashes. New payment options do not establish a new independent provider.

Private outcome intake

Enrolled producers can send POST /api/intelligence/outcomes using their producer signing key. The request binds task and attempt IDs to the service, charge, result fingerprint and a versioned evaluation. See the outcome schema and signing example.

Retries must reuse the event ID and unchanged body. Test and live records stay separate. HMAC verifies the sender, not the truth of their evaluation. Optional retained result evidence is checked against the same producer and task. Outcome records and reported cost summaries require operator access and never automatically affect public integrity.

Connect an application

Create a connection in Operator tools for AP2, A2A, MCP, UCP or ACP. Your application forwards records it is authorized to share to POST /api/protocol-events.

{
  "schema": "inferenceview.protocol.v1",
  "protocol": "ap2",
  "event_id": "your-stable-event-id",
  "event_type": "your-native-event-type",
  "event_time": 1789150000,
  "environment": "test",
  "record": { "native": "application record" }
}

Send X-IV-Connection, X-IV-Timestamp (Unix seconds), and X-IV-Signature: HMAC-SHA256 of timestamp + "." + the exact request body, using your connection key. Deliver within five minutes; reuse the event ID and unchanged body on retries.

Records stay private. Test and live events are separate. This forwarding envelope verifies sender authentication and byte integrity; native protocol signatures, permissions, settlement and outcomes require separate validation.