Agentbodega Mcp

Use this before search_catalog when you have a plain-language task and want AgentBodega to choose the best matching paid route at the lowest useful cost. It calls the free /api/plan planner, returns a recommended endpoint, alternatives, required inputs, examples, and x402 handoff notes. It never executes paid endpoints or creates payments.

Use this first when you need to choose an AgentBodega paid data endpoint. It fetches the live directory and returns matching endpoint summaries with key, path, price, category, tags, required inputs, and example request. It never executes paid endpoints or creates x402 payments.

Use this after search_catalog when you know the endpoint key, title, path, or URL and need the complete contract before paying. It returns method, URL, price, category, tags, long description, required inputs, input/output schemas, example request, and output example when available. It does not call the paid endpoint.

Use this after selecting an endpoint to prepare an HTTP request an agent or user can run outside MCP. It returns curl and JavaScript snippets with the example JSON body, an X-PAYMENT placeholder, and x402 verification notes. It does not fetch a live 402 challenge, spend funds, or execute the paid call.

Use this when an agent needs to understand how AgentBodega x402 and L402 payment discovery work before making paid HTTP calls. It explains the blockchain-settled per-call model, discovery URLs, balance source of truth, optional owner-approved savings offers, and an optional sample challenge request. It does not validate wallets, issue discounts, or perform payments.