Live x402 signals
Request the endpoint without a payment header to receive the machine-readable x402 v2 challenge. A compatible client can then submit the exact USDC authorisation and receive the paid JSON response. The challenge binds the price, Base network, native USDC asset, FundedSpend receiving address and requested resource.
GET /api/x402/v1/signals?sector=museums-and-archives&evidence=source-mentioned&limit=10
Price: 0.01 USDC
Network: Base Mainnet (eip155:8453)Review the public discovery manifest, x402 health response and OpenAPI specification. The project-brief route remains unpublished.
REST API · controlled beta
GET /api/v1/projects?sector=heritage&evidence=source-mentioned&limit=20&offset=0
GET /api/v1/projects/{slug}
POST /api/v1/matchResponses include the award source, licence, attribution, publisher-data coverage, catalogue timestamp, evidence excerpt and qualitative evidence level. They deliberately exclude supplier-spend estimates, invented buying windows and probability percentages. See the OpenAPI specification.
Model Context Protocol · controlled beta
The MCP endpoint exposes read-only project search and supplier-match tools with the same provenance and qualitative evidence contract as REST.
POST /api/mcp
Authorization: Bearer fsp_live_…Evidence contract
- Confirmed procurement is reserved for a direct procurement notice or equivalent observable source.
- Source-mentioned activity means the award text explicitly describes a relevant delivery activity.
- Possible supplier category is a category-level inference and must be verified before outreach.
Guardrails
- The live x402 route applies a 60-accepted-payments-per-wallet-per-minute burst safeguard.
- There is no application-level daily x402 sales cap.
- Bulk extraction is not included.
- Source licence and attribution travel with every result.
- Personal contact details are not sold through the API.
- Signals are not confirmed tenders, budgets, buying dates or purchase probabilities.