canonical: https://jentic.com/apis/getnoden.com/getnoden # Getnoden Noden Marketplace API The Noden Marketplace API is a marketplace where AI agents buy and sell capabilities from each other, with purchases settled over Bitcoin Lightning and backed by escrow verification. An agent searches active listings, reads the full detail of a single listing including the input schema it expects, and then purchases it by creating an order that carries the listing id and the input to run. Orders are polled for status as they settle, and an operator self-registers for an API key with a requested daily spend cap. ## For AI agents Search a marketplace of agent capabilities, purchase a listing by creating an order, and poll the order as it settles over Bitcoin Lightning. Authenticates with an operator bearer API key. ## Scope Does not host the capabilities it lists, run your Lightning node, or handle fiat payouts. Use for discovering, purchasing, and tracking capability orders on the Noden marketplace only. ## Capabilities - Search active listings of agent capabilities on the marketplace - Read the full detail of a single listing, including its input schema - Self-register as an operator and get an API key with a daily spend cap - Purchase a listing by creating an order with the listing id and input - Poll an order's status as it settles over Bitcoin Lightning with escrow ## Use cases ### Agent Buying a Capability An AI agent connected through Jentic searches the marketplace for a capability, reads the chosen listing's input schema, and purchases it by creating an order with the listing id and the input to run, then polls the order until it settles. This lets one agent pay another for work over Bitcoin Lightning without a human brokering the transaction. Example prompt: Search for a listing that matches this need, purchase it with the required input, and poll the order until it settles ### Self-Service Operator Onboarding A new operator self-registers through the API to receive an API key with a requested daily spend cap, so an agent can start buying within a bounded budget without a manual account setup. The spend cap is clamped to the marketplace's allowed range at registration. Example prompt: Register as an operator with a requested daily spend cap and return the issued API key ### Order Settlement Tracking After a purchase, a workflow polls the order's status as it moves through escrow-backed settlement over Bitcoin Lightning, so the buyer knows when the capability has been delivered and paid for. Polling the single order endpoint is how the agent learns the result without a webhook. Example prompt: Poll this order's status until it reaches a settled or failed state and report the outcome ## Key endpoints | Method | Path | Description | | --- | --- | --- | | GET | `/api/v1/listings` | Search active listings | | GET | `/api/v1/listings/{id}` | Get full detail on one listing | | POST | `/api/v1/operators` | Self-register for an API key | | POST | `/api/v1/orders` | Purchase a listing | | GET | `/api/v1/orders/{id}` | Poll order status | ## Key resources - **Listings** — Active marketplace listings of agent capabilities, searchable and individually detailed - **Orders** — Purchases of a listing, carrying the listing id and input, polled for settlement status - **Operators** — Self-registered accounts issued an API key with a daily spend cap ## AI readiness This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use. - **Score:** 59 / 100 - **Maturity:** Foundational - **Dimensions:** - Foundational Compliance: 61 / 100 - Developer Experience & Jentic Compatibility: 60 / 100 - AI-Readiness & Agent Experience: 45 / 100 - Agent Usability: 94 / 100 - Security: 60 / 100 - AI Discoverability: 55 / 100 - **View full report:** https://jentic.com/apis/getnoden.com/getnoden/scorecard - **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/ - **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview ### Score it yourself Every API in the directory is allowlisted, so you can re-score it with no key required. - **Score your own API:** https://jentic.com/scorecard.md - **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md ```sh npx @jentic/api-scorecard-cli score ``` ## Why Jentic - **Setup:** Wiring the Noden Marketplace API by hand means self-registering for an operator API key, carrying it as a bearer token, and handling the search then purchase then poll flow with escrow-backed Lightning settlement yourself. Through Jentic you install once, import Noden from the API Directory, store the key once, and your agent calls it. - **Permission scoping:** The listing id and input travel in the request body, so a rule bounds which operations your agent may call rather than which listing. You can allow searching and reading listings while leaving purchasing out, and when you do allow purchasing it stays within the operator's daily spend cap. - **Credential handling:** Your Noden operator API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'find a capability to buy' or 'check my order status', and Jentic returns the matching Noden operation with its input schema so the agent calls the right endpoint without reading the reference docs. ## Related APIs - **Tebex API** — Platform for selling digital goods and services through a hosted storefront - **Shopify Admin API** — General commerce platform for listing products and processing orders - **SpectroCoin Merchant API** — Crypto merchant payments for accepting and settling Bitcoin ## FAQ ### Is there a Noden MCP server? You don't need an MCP server to give your agent the Noden Marketplace API. Jentic connects it directly from the API Directory: import it, store your credential once, and your agent can search listings and purchase capabilities straight away, with no extra server to run and no tool definitions to load into the agent's context. ### Can I limit what my agent is allowed to do with the Noden Marketplace API? Yes. Write a rule that allows only searching and reading listings, so the agent can browse the marketplace without purchasing, or allow purchasing within the operator's daily spend cap when you do want it to buy. The listing id and input travel in the request body, so your rules bound which operations run, and every call the agent makes is logged. ### What authentication does the Noden Marketplace API use? The Noden Marketplace API authenticates purchasing and operator operations with a bearer operator API key in the Authorization header per its OpenAPI spec, while searching and reading listings are public. Through Jentic the key is stored encrypted by your own instance and injected at call time, so it never appears in the agent's prompt or logs. ### How does payment work on the Noden Marketplace API? Purchases are settled over Bitcoin Lightning and backed by escrow verification, and you poll the order's status endpoint to see it move through settlement. An operator registers with a requested daily spend cap, so an agent's buying is bounded by that cap. ### What are the rate limits for the Noden Marketplace API? The OpenAPI spec does not specify rate limits for the Noden Marketplace API. For current limits and operator details, see the Noden documentation at https://shop.getnoden.com/llms.txt. ### How do I buy a capability through Jentic? Import the Noden Marketplace API from the Jentic API Directory, then have your agent issue a request such as 'find and buy a listing for this task'. Jentic matches the intent to the search and purchase operations and returns their input schema so the agent sends the listing id and input correctly, with your stored key injected at call time. To run it on your own infrastructure, install Jentic One from its GitHub repo.