A Kite-targeted deployment returns the expected HTTP 402 without breaking Base.
Kite Agent Passport Readiness
Ready to watch. Not switching rails.
A readiness pack for buyer agents that may use Kite Agent Passport for delegated x402 payment control while Agent Research Desk keeps production settlement on the proven Base rail.
Base remains active Kite proof not run No auto-spend Buyer-side compatibilityeip155:8453
Passport can be tracked as a buyer-side path, not an accepted ARD rail.
Requires a separate small approved proof window.
No buyer prompts, wallet history, raw feedback, or paid response bodies are public.
How to use it now
Buyer agents keep control.
- Use Kite Agent Passport on the buyer side if your agent already has a Passport-controlled wallet and budget.
- Inspect /docs.json, choose an ARD route, and send the normal unpaid probe first.
- Pay the listed ARD route price only through your own x402 client and approved budget.
- Treat ARD's current settlement proof as Base mainnet proof until a separate Kite proof run exists.
Guardrails
No production claim without proof.
- Do not change the working Base mainnet x402 middleware, facilitator, seller wallet, endpoint paths, or route prices.
- Do not run paid Kite purchases from this readiness pack.
- Do not create Passport sessions or delegate spending from this service.
- Do not claim Kite settlement is accepted until unpaid 402, paid 200, settlement, discovery, and rollback checks pass.
- Do not expose buyer prompts, wallet-level request history, raw feedback comments, watched subjects, or paid response contents.
Proof gate before acceptance
Kite needs its own verification window.
One small approved paid test returns HTTP 200 with structured JSON.
The seller wallet receives the expected settlement on the intended Kite-compatible path.
Discovery surfaces show the intended network and route metadata after proof.
Base remains the default active rail after the proof window is removed.
Source and product links