Compatibility checks your agent can prove
For teams building shopping agents, automation platforms, and repair or product-research services. Your agent sends two product identifiers and gets an evidence-backed answer with a signed receipt. No merchant integration, checkout access or payment details involved.
What's real today, and what isn't yet
| Capability | Status | Notes |
|---|---|---|
| Compatibility and installation-fit checks (MCP + HTTP API) | Available | Seven categories; see coverage. |
| Signed receipts with valid-until dates | Available | EdDSA JWS; check with verify_receipt. Proves what we said and when, not that it's right. |
| Outcome reports with verification levels | Available | Self, agent, partner and order-confirmed. Only partner and confirmed reports raise confidence. |
| Discontinued-part cross-references | Available | Early: a handful of replacement parts so far. |
| Per-key usage reporting and higher limits | Pilot | GET /v1/usage with your key; 1,200 calls an hour. |
| Dataset access for evaluation | Pilot | Paged export of the graph with sources, for approved keys. |
| Categories added on request | Pilot | Tell us what your agent gets asked. |
| Paid access: x402 (USDC) and prepaid card credits | Planned | Built and tested; not switched on yet. Nothing is charged during the pilot. |
| Purchase guarantees | Not offered | We won't guarantee purchases until we understand real failure rates. |
What we'd ask of you
- Send real questions your agent gets, including the ones we can't answer yet.
- Tell us what your agent does today instead (search manufacturer sites, guess, ask the user), so we can measure whether we save time or mistakes.
- Report outcomes when you learn them, with order details where you can.