p402.io valid
P402.io
AI infrastructure for payment processing, token metering, intelligent routing, distributed tracing, compliance auditing, and spend optimization. Production-grade. OpenAI-compatible. Settles micropayments on-chain.
Their llms.txt
The beginning of the file, from our validated copy saved 2026-10-24T20:12:07.573Z. Cached copy · Source on p402.io
# P402.io
> AI infrastructure for payment processing, token metering, intelligent routing, distributed tracing, compliance auditing, and spend optimization. Production-grade. OpenAI-compatible. Settles micropayments on-chain.
P402 is the infrastructure layer that sits between AI applications and AI providers — the same way a payment network sits between merchants and banks. It handles routing, authorization, metering, settlement, and governance so your application makes one API call and P402 handles the rest.
---
## What P402 Does
**Payment Processing** — EIP-3009 gasless USDC settlement on Base L2. HTTP 402 becomes a machine-native payment primitive. Facilitators execute on-chain transfers; users pay zero gas.
**Token Metering** — Per-token AI billing tracked at request granularity. Every token counted, costed, and attributed to a department, project, or employee. Real-time dashboards. Budget enforcement. Overage alerts.
**Intelligent Routing** — 300+ models across 13 providers. Four routing modes: `cost`, `speed`, `quality`, `balanced`. Semantic cache cuts redundant LLM calls. Gemini-powered Protocol Economist optimizes routing decisions asynchronously.
**Distributed Tracing** — Every request traced end-to-end: model selected, provider latency, tokens used, cost incurred, cache hit/miss, routing decision, settlement result. SSE real-time trace viewer. Full audit trail in `traffic_events`.
**Compliance Auditing** — Immutable audit log for every AI interaction. Department attribution via `X-P402-Department`, `X-P402-Project`, `X-P402-Employee` headers. Proof-of-settlement receipts. HIPAA-ready audit trails for healthcare. Compliance bundles for legal. Verifiable spend records for finance.
**Spend Optimization** — AI-generated recommendations from Gemini Protocol Economist. Model mix analysis. Budget pacing (day-of-month projection). Semantic cache ROI. Provider cost comparisons. Enterprise dashboard with department budgets, top spenders, project breakdown.
---
## P402 Meter — Per-Token AI Billing
P402 Meter is the per-token billing system built on Tempo mainnet (chain 4217) using TIP-20 stablecoins (USDC.e, USDT0, cUSD, pathUSD, and 6 more).
**Key capabilities:**
- Per-request token counting with department/project/employee attribution
- Budget caps enforced in real time — requests blocked when budget exhausted
- On-chain settlement proofs (Tempo USDC.e, ERC-20 `transfer`)
- Full model mix analytics: which models each team is using and what it costs
- Semantic cache: identical or near-identical queries served from cache, cost = $0
- Enterprise dashboard: department budgets, top employees by spend, project breakdown, recent sessions, optimization findings
**Industry demos (live):**
- `/meter/healthcare` — HIPAA-grade audit trail, clinical AI compliance, department cost allocation
- `/meter/legal` — matter-level billing, privilege log, multi-jurisdictional routing, per-token invoicing
- `/meter/real-estate` — property-contextual AI,
…
Related sites
Similar publisher descriptions and documentation. Similarity does not imply affiliation or equivalent capabilities.
| Domain | Title | Category | Country | Authority | llms.txt | llms-full.txt | Save |
|---|---|---|---|---|---|---|---|
| ap2-protocol.org | AP2 - Agent Payments Protocol Documentation | documentation Finance and payments AI and machine learning +2 | — | 55 | ✓ | ✓ | |
| cai.com | CAI.com | interface AI and machine learning AI agents and MCP +1 | — | 59 | ✓ | ||
| xpay.sh | xpay — Content Marketplace + Tool Layer for AI Agents | interface AI and machine learning AI agents and MCP +1 | US | 47 | ✓ | ✓ | |
| agentshare.dev | AgentShare — Agent-paid API for autonomous agents | interface AI agents and MCP APIs and SDKs | — | 46 | ✓ | ✓ | |
| mpp.dev | MPP — Machine Payments Protocol | interface Finance and payments APIs and SDKs +1 | US | 57 | ✓ | ✓ | |
| prometheusprotocol.org | Prometheus Protocol | documentation AI agents and MCP Crypto and Web3 | US | 48 | ✓ | ✓ | |
| ausca.com | Ausca | interface AI agents and MCP APIs and SDKs | — | 65 | ✓ | ✓ | |
| nevermined.ai | Nevermined | interface AI agents and MCP Finance and payments +1 | US | 52 | ✓ |
Machine-readable: GET /v1/resolve?q=p402.io · GET /v1/domain/p402.io · this page as Accept: application/json or text/markdown · MCP lookup_domain
Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.
Own or manage this website?
If you own or manage p402.io, you can update its listing and review file health, discovery activity and score history.
Manage this listing — optional
What verification unlocks
See how your site is discovered—and control what agents see.
- See your website in the map
Review your indexed topics, nearby publishers sharing headings, measured listing exposure and map snapshots in a private report for your website.
- Control what agents see
Edit your listing description, tags, public contact details and additional llms.txt paths. Publish your terms for automated access, attribution and pricing.
- Make your profile eligible for search
A valid, listed, unblocked, verified profile can appear in our publisher sitemap and become eligible for search-engine visibility. Search engines decide what to index and rank.
- Appear in our llms-full.txt
Eligible verified publishers are listed by name, with their file links and summaries, in the service overview agents can read.
Free. No account registration, backlink or payment required. Public discovery remains available without verification.
Let your coding agent verify it
If your coding agent is authorized to manage this website, paste these instructions into it.
Claim my listing on Agent Web Map for p402.io:
1. POST https://agentwebmap.com/v1/sites/p402.io/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://p402.io/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/p402.io/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/p402.io).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verifyCorrections or removal requests: contact the directory.