REST / OpenAPI
Software, scripts, internal tools, and automation
/api/v1/openapiPublic discovery; paid routes use x402Choose REST, MCP, the Codex plugin bundle, or A2A. Every method reaches the same source-backed service and uses the same payment and security boundaries.
https://x402.contractorsDiscovery does not require a wallet. Paid analysis never runs without explicit authorization and verified settlement.Software, scripts, internal tools, and automation
/api/v1/openapiPublic discovery; paid routes use x402Codex, ChatGPT, Claude, and compatible AI hosts
/mcpFree discovery tools; paid analysis requires approvalReusable skill and remote MCP configuration
amlitio/florida-build-intelligenceRepository access is requiredStructured agent-to-agent construction requests
/.well-known/agent-card.jsonJSON-RPC with explicit project dataUse the Streamable HTTP endpoint https://x402.contractors/mcp. Start with discovery or tools/list, then call a free source tool. The paid project-analysis tool is intentionally marked financially consequential and must never be invoked without the user approving the exact x402 charge.
curl -sS -X POST https://x402.contractors/mcp \
-H "Content-Type: application/json" \
-H "Accept: application/json, text/event-stream" \
-H "MCP-Protocol-Version: 2026-07-28" \
-d '{"jsonrpc":"2.0","id":1,"method":"server/discover","params":{}}'[mcp_servers.x402_contractors] url = "https://x402.contractors/mcp"
claude mcp add --transport http x402-contractors https://x402.contractors/mcp
{
"mcpServers": {
"x402-contractors": {
"type": "http",
"url": "https://x402.contractors/mcp"
}
}
}The plugin source belongs to the GitHub repository below. Use the repository owner and repository name separated by a slash—do not use a backslash or replace the slash with @.
codex plugin marketplace add amlitio/florida-build-intelligence --ref master codex plugin marketplace list codex plugin add x402-contractors@x402-contractors
x402-contractors appears in the marketplace list.GITHUB_PAT_TOKEN affects the separate GitHub MCP client; it is not an x402 wallet error.Use JSON endpoints for applications, SaaS products, scripts, and low-code automation. Browser visits may open a human dashboard; send Accept: application/json or ?format=json for machine-readable output.
curl -sS -H "Accept: application/json" \ "https://x402.contractors/api/v1/sources?format=json"
Discover the signed service description first, then send a structured project message. A2A identity, data authorization, and payment authorization remain separate controls.
curl -sS https://x402.contractors/.well-known/agent-card.json
curl -sS -X POST https://x402.contractors/a2a \
-H "Content-Type: application/json" \
-d '{"jsonrpc":"2.0","id":"request-1","method":"message/send","params":{"message":{"role":"user","parts":[{"kind":"data","data":{"address":"Miami-Dade County, FL","projectType":"Commercial renovation","scope":"Official permit and procurement source research"}}],"messageId":"message-1"}}}'Use x402 v2 headers: PAYMENT-REQUIRED, PAYMENT-SIGNATURE, and PAYMENT-RESPONSE. Use a unique Idempotency-Key. Never put a private key, seed phrase, facilitator secret, or provider key in browser code, MCP configuration, plugin files, GitHub, or support messages.
Inspect current payment readiness · Read the payment protocol reference
Use HTTPS and the exact x402.contractors host. Do not follow a payment request to an unrelated domain.
Enable only the tools and data scopes the client needs. Keep administrative collection routes separate from public discovery.
Bound input length, reject malformed requests, preserve official-source provenance, and require human review for filings or regulated actions.
Show the amount, network, asset, and recipient before authorization. Never convert a discovery request into an automatic purchase.
Reconcile request ID, nonce, transaction hash, and settlement state. Do not retry a pending transaction blindly.
Return citations and limitations, exclude secrets, use no-store caching for protocol responses, and log bounded error codes rather than credentials.
server/discover, initialize, and tools/list.This release verifies steps 1–6 automatically. Step 7 requires an owner-configured production wallet, a mainnet-capable facilitator, and a deliberately authorized live transaction; it is never simulated or claimed.