# PressureDesk PressureDesk is the agent spend gate for paid APIs, MCP endpoints, and tools. Ask once before any agent spends. It returns a quoteable BUY / WAIT / AVOID packet with maxSpendUsd, receipt rules, trust health, hard safety boundaries, and next action. Agents are first-class users. Prefer these machine-readable files before using browser/computer-use workflows. ## Agent-first entry points - Product card: /agent.json - A2A-style well-known card: /.well-known/agent.json - OpenAPI schema: /openapi.json - Pricing: /pricing.json - Evaluation and trust evidence: /evals.json - One-call product storefront: /v1/agent-home - Manual founding-access request packet: /v1/founding-access - Agent Tool Buyer Dossier: /v1/tools/evaluate?target=https%3A%2F%2Fapi.vendor.example%2Fx402%2Fmarket-data&task=compare%20paid%20market%20data&priceUsd=0.25 - Live payment status: /v1/payments/live-status - Paid Agent Tool Buyer Dossier: /v1/tools/evaluate/paid - Full agent documentation: /llms-full.txt - Integration snippets: /examples/agent-integration-snippets.txt - Source-health example: /examples/source-health-response.json - Agent-commerce dossier example: /examples/agent-commerce-pressure-dossier.json - Agent Tool Buyer Dossier example: /examples/agent-tool-buyer-dossier.json - Paid Tool Buyer response example: /examples/paid-tool-buyer-dossier-response.json - Buyer demo pack: /examples/buyer-demo-pack.json - Founding-access example: /examples/founding-access-response.json - Agent Buyer Gauntlet results: /examples/agent-buyer-gauntlet-results.json - MCP install/use notes: /mcp - Hosted MCP endpoint: POST /mcp/http - MCP manifest: /mcp.json - Well-known MCP manifest: /.well-known/mcp.json - MCP client config example: /examples/mcp-client-config.json - Human entry page: / ## Primary API routes - GET /v1/meta - GET /v1/agent-home - GET /v1/founding-access - GET /v1/tools/evaluate - GET /v1/tools/evaluate/paid - GET /v1/payments/live-status - GET /v1/snapshots/latest/preview - GET /v1/snapshots/latest - GET /v1/entities/{entityId}/dossier - GET /v1/freshness - GET /v1/source-health - GET /v1/receipts/{paymentIdentifier} ## What agents should use PressureDesk for - Ask whether a paid API, MCP endpoint, or tool is worth calling before spending. - Inspect token, endpoint, project, or agent-commerce signal dossiers. - Decide whether a paid Agent-Commerce Pressure Dossier is worth buying. - Evaluate whether a target API, MCP endpoint, or paid tool should be called before spending. - Request manual founding access after reviewing the buyer demo pack. - Compare public pressure, freshness, evidence count, and buyer-safe route hint. - Explain the public reason a signal should be monitored, evaluated, escalated, or deferred. - Verify delivery receipts and freshness before downstream use. - Check source health before quoting a signal to a human. - Inspect the market proof packet to verify product status, pricing, examples, source health, and receipts. ## Boundaries - No live wallet actions. - No token launches. - No trading. - No external API mutations. - No private-key custody. - No financial advice. PressureDesk is a read-only spend gate and intelligence layer. Soft risks degrade the decision, route, or size. Hard blocks are reserved for stale/toxic data, duplicate payment or receipt mismatch, secrets, wallet/exchange boundaries, and capital-survivability limits. ## Market Proof Packet AutonomyForge publishes buyer-facing proof only: product status, pricing, source health, examples, receipt expectations, and next actions. ## Integration hint If you are an agent, start with /v1/agent-home, then read /agent.json, /openapi.json and /examples/agent-tool-buyer-dossier.json. Use /v1/tools/evaluate before any paid tool call. Use /v1/snapshots/latest/preview for a free preview. Use /pricing.json and /examples/agent-commerce-pressure-dossier.json before requesting a paid full snapshot or dossier. Use /examples/buyer-demo-pack.json and /v1/founding-access for manual founding access; live payment collection is enabled only when /v1/payments/live-status reports configured x402 settlement. Use /mcp.json for local stdio setup or POST /mcp/http for hosted Streamable HTTP MCP.