Install Jentic One Beta

Connect the AurasPay REST API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the AurasPay REST API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fauraspay.com%2Fauraspay" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fauraspay.com%2Fauraspay" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with AurasPay REST API.

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

GET STARTED

Start building with AurasPay REST API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use AurasPay REST API for, with concrete tasks.

★ 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.

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.

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.

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

6 endpoints — the auraspay rest api is a server-side merchant api for collecting crypto payments through payment links.

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

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

Why Jentic?

What agents get from Jentic-routed access to this vendor.

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 isolation

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.

Intent-based discovery

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.

FAQs

Specific to using AurasPay REST API through Jentic.

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.

AurasPay REST API

AI ReadinessAI-Aware (B)65/100

See full scorecard

Official vendor OpenAPI document · agent-readyPaymentsPayment Processingbearer, apiKey6 EndpointsREST

For 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.

Use for: Create a crypto payment link for a customer order, List the payment links on my merchant account, Get the details of a specific payment link, Verify that a payment link was paid

Not supported: Does not handle fiat payouts, accounting, or refunds. Use for creating and verifying crypto payment links only.

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.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

100

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A+Signals: 4

99%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

100%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: B+Signals: 4

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

75%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: DSignals: 4

36%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

46%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: CSignals: 1

55%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: B-Signals: 1

62%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the AurasPay REST API to your agent

Capabilities

Start building with AurasPay REST API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

AurasPay REST API

Jentic AI Readiness Score

AurasPay REST API

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness