canonical: https://jentic.com/apis/auraspay.com/auraspay # AurasPay REST API The AurasPay REST API is a server-side merchant API for collecting crypto payments through payment links. A merchant creates a payment link, lists and reads the links on the account, and verifies the transaction once a customer pays. It also exposes the authenticated merchant account and the current set of supported assets and networks, which depend on the network and the merchant's configuration. ## For AI agents Collect crypto payments as a merchant: create payment links, list and read them, verify a link's transaction after payment, and read the account and supported assets. Authenticate with a bearer token or an X-API-Key header. ## Scope Does not handle fiat payouts, accounting, or refunds. Use for creating and verifying crypto payment links only. ## Capabilities - Create crypto payment links for a merchant to collect a payment - List and read the payment links created on an account - Verify a payment link's transaction once a customer pays - Read the authenticated merchant account - List the crypto assets and networks currently available for payment ## Use cases ### Crypto Checkout Links An agent creates a payment link for a customer order and hands the link over for payment, then verifies the transaction once the customer pays. AurasPay returns the link and its verification state, so the agent can collect a crypto payment without building wallet handling or settlement logic. Example prompt: Call POST `/api/v1/payment-links` to create a link for an order, then POST `/api/v1/payment-links/{id}/verify` after the customer pays ### Payment Reconciliation A reconciliation workflow lists the payment links on a merchant account and reads each one's state to confirm which orders were paid. Because the agent can list links and read the account, it reconciles collected payments against open orders without a manual export. Example prompt: Call GET `/api/v1/payment-links` to list links, then GET `/api/v1/payment-links/{id}` to read each one's payment state ### AI Agent Integration via Jentic An AI agent reaches the AurasPay REST API through Jentic without holding the merchant credential itself. It searches by intent, receives the matching operation with its input schema, and executes the call with the credential injected at run time, so creating and verifying payment links becomes a step in a larger commerce workflow. Example prompt: Search Jentic for 'create a crypto payment link', load the POST `/api/v1/payment-links` schema, and execute it with Jentic-managed credentials ## Key endpoints | Method | Path | Description | | --- | --- | --- | | POST | `/api/v1/payment-links` | Create a payment link | | GET | `/api/v1/payment-links` | List payment links | | GET | `/api/v1/payment-links/{id}` | Get a payment link | | POST | `/api/v1/payment-links/{id}/verify` | Verify a payment link transaction | | GET | `/api/v1/account` | Get the authenticated merchant account | | GET | `/api/v1/supported-tokens` | List supported assets and networks | ## Key resources - **Payment Links** — Create, list, read, and verify payment links via `/api/v1/payment-links` and `/api/v1/payment-links/{id}/verify` - **Account** — Read the authenticated merchant account via `/api/v1/account` - **Supported Assets** — List the currently supported assets and networks via `/api/v1/supported-tokens` ## 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:** 65 / 100 - **Maturity:** AI-Aware - **Dimensions:** - Foundational Compliance: 100 / 100 - Developer Experience & Jentic Compatibility: 69 / 100 - AI-Readiness & Agent Experience: 46 / 100 - Agent Usability: 94 / 100 - Security: 55 / 100 - AI Discoverability: 63 / 100 - **View full report:** https://jentic.com/apis/auraspay.com/auraspay/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 AurasPay by hand means choosing between its bearer token and X-API-Key schemes, handling the per-payment platform fee, and verifying each transaction yourself. Through Jentic you install once, import AurasPay from the API Directory, store the credential once, and your agent calls it. - **Permission scoping:** AurasPay carries the payment-link id in the URL path and the order details in the request body, so a rule bounds which operations your agent may call. You choose the operations it may use, such as listing and reading links, so the create operation that collects a payment is not included unless you add it. - **Credential handling:** Your AurasPay credential 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 'create a crypto payment link' or 'verify a payment', and Jentic returns the matching AurasPay operation with its input schema so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **NOWPayments** — Crypto payment gateway for accepting many coins - **CryptAPI** — Non-custodial crypto payment processing by address - **Coinbase** — Crypto exchange and account services ## FAQ ### What authentication does the AurasPay REST API use? The AurasPay REST API authenticates with a bearer token or an API key in the X-API-Key header, per its OpenAPI spec, and either scheme is accepted on its operations. Through Jentic the credential is stored encrypted by your own Jentic One instance and injected at execution time, so it never reaches the agent. ### Can I create and verify a crypto payment link with the AurasPay REST API? Yes. POST `/api/v1/payment-links` creates a link for a merchant to collect a payment, and POST `/api/v1/payment-links/{id}/verify` confirms the transaction once the customer pays. GET `/api/v1/supported-tokens` lists the assets and networks available, which depend on the network and your merchant configuration. ### What are the rate limits for the AurasPay REST API? The AurasPay OpenAPI spec does not specify rate limits. Watch for HTTP 429 responses and check AurasPay's documentation for the current limits before issuing payment links at high volume. ### How do I create a crypto payment link with the AurasPay REST API through Jentic? Search Jentic for 'create a crypto payment link', and it returns the AurasPay operation with its input schema. Load the schema and execute POST `/api/v1/payment-links` with the credential injected at run time. To run it on your own infrastructure, install Jentic One from its GitHub repo. ### Is there an AurasPay MCP server? You don't need an MCP server to give your agent the AurasPay REST API. Jentic connects it directly from the API Directory: import it, store your credential once, and your agent calls the payment-link operations it needs. Operations are discovered on demand, so no extra server's tool definitions sit in the agent's context. ### Can I limit what my agent is allowed to do with the AurasPay REST API? Yes. Write a rule that allows only the read operations, such as listing links and reading supported tokens, and add the create operation only when the agent needs to issue new links. Every call runs through your own instance where it is logged for review, so a payment-collecting operation is never silently available.