Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the GriffNode 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%2Fgriffnode.com%2Fgriffnode" | shStep 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%2Fgriffnode.com%2Fgriffnode" | sh
jentic register # connects your agent to your Jentic One instanceJentic 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.
What an agent can do with GriffNode API.
Accept Bitcoin, Litecoin, Dogecoin, Dash, Ethereum, and ERC-20 token payments
Create a payment transaction or an itemized detailed transaction
Retrieve and list the merchant's transactions
Read current crypto and fiat exchange rates
List supported cryptocurrencies and the merchant's configured wallets
GET STARTED
Read merchant plan, usage, balances, and transaction analytics
Patterns agents use GriffNode API for, with concrete tasks.
★ Agent-run crypto checkout
An AI agent can accept cryptocurrency for an order through GriffNode by creating a payment transaction, returning the payment details to the buyer, and retrieving the transaction to confirm it. Live and test modes share one base URL, switched by the secret-key prefix, so an agent can rehearse the flow safely. Connected through Jentic, the agent calls only the transaction operations it needs.
Create a payment transaction for an order amount, return the payment details, and retrieve the transaction to confirm its status
Rate-aware pricing
Merchants quoting prices in crypto need current rates. GriffNode returns current crypto and fiat exchange rates denominated in USD, and lists every supported cryptocurrency and token. An agent can price an order in a chosen coin before creating the transaction.
Read the current USD rate for a cryptocurrency and use it to quote an order amount
Merchant reporting
Finance teams reconcile crypto payments and monitor usage against plan limits. GriffNode exposes transaction analytics, on-platform balances for overage and top-up, and plan and usage details. An agent can pull these to build a reconciliation or alerting workflow.
Retrieve the merchant's transaction analytics and current plan usage for a reconciliation report
15 endpoints — the griffnode api accepts cryptocurrency payments including bitcoin, litecoin, dogecoin, dash, ethereum, and erc-20 tokens through a server-to-server integration authenticated with a secret api key.
METHOD
PATH
DESCRIPTION
/transactions/create
Create a payment transaction
/transactions/create-detailed
Create an itemized transaction
/transactions/list
List the merchant's transactions
/transactions/{transaction_id}
Retrieve a single transaction
/prices
Current crypto and fiat exchange rates
/cryptos/list
List supported cryptocurrencies and tokens
/stats
Merchant transaction analytics
/transactions/create
Create a payment transaction
/transactions/create-detailed
Create an itemized transaction
/transactions/list
List the merchant's transactions
/transactions/{transaction_id}
Retrieve a single transaction
/prices
Current crypto and fiat exchange rates
/cryptos/list
List supported cryptocurrencies and tokens
/stats
Merchant transaction analytics
What agents get from Jentic-routed access to this vendor.
Setup
Wiring GriffNode by hand means managing its live and test secret keys, the two-window rate limits, and the string-versus-number amount formats between responses and webhooks yourself. Through Jentic you install once, import GriffNode from the API Directory, store the secret key once, and your agent calls it.
Permission scoping
GriffNode carries the amount, coin, and transaction id in the path and body, so a rule bounds which operations your agent may call rather than which transaction. You choose the operations it may call, so the billing-checkout operation is not included unless you add it.
Credential isolation
Your GriffNode secret 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.
Intent-based discovery
Agents search Jentic by intent such as 'create a crypto payment' or 'read exchange rates', and Jentic returns the matching GriffNode operation with its input schema so the agent calls the right endpoint without reading the reference docs.
Alternatives and complements available in the Jentic catalogue.
Specific to using GriffNode API through Jentic.
What authentication does the GriffNode API use?
GriffNode authenticates with a secret API key sent as a Bearer token in the Authorization header, per its OpenAPI spec, using a live or test key prefix on the same base URL. The health check and hosted-checkout redirect are public. Through Jentic the secret key is stored encrypted by your own Jentic One instance and injected at execution time.
Can I accept Bitcoin and Ethereum payments with the GriffNode API?
Yes. The transaction operations create a payment in Bitcoin, Litecoin, Dogecoin, Dash, Ethereum, or an ERC-20 token, and you can retrieve or list transactions afterward. The rates operation returns current USD-denominated prices so an order can be quoted in the chosen coin.
What are the rate limits for the GriffNode API?
GriffNode rate-limits each API key in two windows, per minute and per hour, by plan tier, and the OpenAPI spec notes the two windows. Check https://docs.griffnode.com for the per-plan figures.
How do I create a crypto payment with the GriffNode API through Jentic?
Search Jentic for 'create a crypto payment' and it returns the GriffNode create-transaction operation with its input schema, so your agent fills the amount and coin and calls it. Install Jentic One with `curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh`, import GriffNode from the API Directory, and store your secret key once. To run it on your own infrastructure, install Jentic One from its GitHub repo.
Can I limit what my agent is allowed to do with GriffNode?
Yes. Write a rule that allows only the create-transaction and transaction read operations, so the agent can take payments and check their status but cannot start a billing checkout or plan upgrade, and every call it makes is logged.
Is there a GriffNode MCP server?
You don't need an MCP server to connect your agent to GriffNode. Jentic connects it directly from the API Directory: import it, store your credential once, and your agent discovers and calls the operations it needs on demand.
For Agents
Lets an AI agent create cryptocurrency payment transactions, list and retrieve them, and read exchange rates and merchant analytics.
Use for: Create a cryptocurrency payment transaction, I want to accept a Bitcoin payment for an order, Retrieve a single transaction by its id, List the merchant's recent transactions
Not supported: Does not handle fiat card processing, crypto custody, or on-chain settlement. Use for accepting cryptocurrency payments only.
The GriffNode API accepts cryptocurrency payments including Bitcoin, Litecoin, Dogecoin, Dash, Ethereum, and ERC-20 tokens through a server-to-server integration authenticated with a secret API key. Merchants create payment transactions or itemized detailed transactions, list and retrieve them, and read current crypto and fiat exchange rates. It also exposes supported cryptocurrencies, the merchant's configured wallets, plan and usage, on-platform balances, and transaction analytics.
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.
Base layer of spec validity and structural soundness.
Aggregated quality score from linter diagnostics, weighted by severity.
Percentage of `$ref` references that resolve successfully.
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
Structural correctness score based on schema issues using logarithmic dampening.
Clarity, completeness, and ingestion readiness for developers and tooling.
How richly the API is illustrated with examples.
Percentage of examples that conform to their schemas.
Percentage of operations with complete response definitions (success, client error, server error).
Health of API ingestion, bundling, and resolution within Jentic pipelines.
Semantic breadth, depth, and agent comprehension for AI systems.
Coverage of descriptions across API elements.
Coverage of RFC 9457 Problem Details for error responses.
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
Coverage of summaries across operations/tags/info.
Functional utility, complexity comfort, and AI orchestration readiness.
Agent comfort level based on API operational and structural complexity.
Trust, risk posture, and security compliance.
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
Findability, semantic richness, and reasoning readiness.
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>