Install Jentic One Beta

Connect the GhostPay API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the GhostPay 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%2Fghostwareos.com%2Fghostwareos" | 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%2Fghostwareos.com%2Fghostwareos" | 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 GhostPay API.

Create a crypto payment link for a merchant

Look up payment links by wallet address

Retrieve the details of a specific payment link by id

Initiate a payment against a payment link

Initiate a cross-chain send or swap between networks

GET STARTED

Start building with GhostPay API

Explore with Jentic One

View OpenAPI Document

Wallet-Scoped Link Tracking

A merchant dashboard tracks outstanding payment links for a given wallet. GhostPay returns the links associated with a wallet address, so an agent reconciles which links belong to which wallet without maintaining its own index.

Fetch all payment links for a wallet address and report which ones have been paid

Cross-Chain Settlement

An agent settling received funds initiates a cross-chain send or swap to move balances onto the target network. GhostPay exposes a dedicated send/swap operation, so the agent moves funds across chains as a single call rather than orchestrating a bridge manually.

Initiate a cross-chain send to move a settled balance to the target network and record the result

Key Endpoints

5 endpoints — the ghostpay api creates crypto payment links, initiates payments against them, and runs cross-chain sends and swaps.

METHOD

PATH

DESCRIPTION

POST

/links

Create a payment link

GET

/links/{linkId}

Get payment link details

GET

/links/wallets/{wallet}

Get payment links by wallet address

POST

/payments/initiate

Initiate a payment

POST

/sends/initiate

Initiate a cross-chain send or swap

POST

/links

Create a payment link

GET

/links/{linkId}

Get payment link details

GET

/links/wallets/{wallet}

Get payment links by wallet address

POST

/payments/initiate

Initiate a payment

POST

/sends/initiate

Initiate a cross-chain send or swap

Why Jentic?

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

Setup

Wiring GhostPay by hand means handling its bearer API key, tracking the JWT returned by the payment-initiate flow, and coding the cross-chain send call yourself. Through Jentic you install once, import GhostPay from the API Directory, store the key once, and your agent calls the link, payment, and send operations.

Permission scoping

GhostPay carries link-creation and read operations alongside operations that initiate payments and cross-chain sends. You choose the operations your agent may call, so a rule can keep it to creating and reading payment links and leave payment or send initiation out unless you add them.

Credential isolation

Your GhostPay API key is held by your own Jentic One instance, encrypted, and injected into the request as a bearer token 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 'initiate a cross-chain send', and Jentic returns the matching GhostPay operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using GhostPay API through Jentic.

What authentication does the GhostPay API use?

The API uses bearer authentication, sending an API key in the format `gp_live_...` as a bearer token, per its OpenAPI spec. The spec also declares a JWT bearer scheme for tokens returned by the payment-initiate flow. Through Jentic the key is held by your own Jentic One instance and attached to each request at execution time, so it never appears in your agent's prompt or logs.

Can I create crypto payment links with the GhostPay API?

Yes. The create-link operation returns a payment link you can share, and you retrieve it later by link id or list links by wallet address. Your agent builds a shareable crypto checkout without wiring up a wallet integration directly.

What are the rate limits for the GhostPay API?

The OpenAPI spec does not specify rate limits. Check the GhostPay documentation at https://api2.ghostwareos.com for current limits before running high-volume payment flows.

Is there a GhostPay MCP server?

You do not need an MCP server to give your agent the GhostPay API. Jentic connects it directly from the API Directory: import it, store your key once, and your agent calls the payment-link and send operations on demand without loading an extra server's tool definitions into its context.

Can I limit what my agent is allowed to do with the GhostPay API?

Yes. Write a rule that allows only the operations your agent needs, such as creating and reading payment links, so it cannot initiate payments or cross-chain sends unless you add those operations. You choose what the agent may call, and every call it makes is logged.

How do I create a payment link through Jentic?

Install the Jentic One command line with `curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh`, then add the GhostPay API from the Jentic directory and search by intent such as 'create a crypto payment link'. Jentic returns the matching operation with its input schema so your agent builds a valid request. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Ghostwareos GhostPay API

AI ReadinessAI-Aware (A-)71/100

See full scorecard

Community OpenAPI document · agent-readyPaymentsPayment Processingbearer5 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Create crypto payment links, initiate payments against them, look up links by wallet or id, and start cross-chain sends and swaps through the GhostPay API.

Use for: I need to create a crypto payment link for a checkout, Get the details of a payment link by its id, List all payment links tied to a wallet address, Initiate a payment against an existing payment link

Not supported: Does not host wallets, provide market pricing, or handle fiat card processing. Use for crypto payment links, payments, and cross-chain sends only.

The GhostPay API creates crypto payment links, initiates payments against them, and runs cross-chain sends and swaps. A merchant creates a payment link, shares it, and then looks up links by wallet address or by link id to track them. Payments are initiated against a link, and a separate operation initiates a cross-chain send or swap so funds can move between networks.

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: A-Signals: 4

25%

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: C-Signals: 4

51%

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.

50%

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: B+Signals: 1

68%

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

68%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the GhostPay API to your agent

Capabilities

Start building with GhostPay API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Ghostwareos GhostPay API

Jentic AI Readiness Score

GhostPay 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