Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Liquid Agent: Money Tools for AI Agents, 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%2Fliquidagent.ai%2Fliquidagent" | 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%2Fliquidagent.ai%2Fliquidagent" | 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 Liquid Agent: Money Tools for AI Agents API.
Bridge USDC from Base to chains such as Arbitrum, OP Mainnet, Polygon, and Avalanche, or from Arc to Base, with one x402 payment
Quote a bridge route for free and track a transfer's Circle attestation and mint state by burn transaction
Check USDC and gas balances of an address across CCTP chains
Preview, buy, rebalance, send, or redeem shares of a tokenized NVIDIA, Apple, Meta, and Alphabet basket, receiving a transaction to sign
GET STARTED
Read a vault's NAV, holdings, and current versus target weights, and get basket rebalancing signals
Get the official Polymarket price to beat and live Chainlink price for BTC, ETH, SOL, or XRP up/down markets
Get gas sponsored on Base, Polygon, or Solana by paying the fee in USDC over x402
Patterns agents use Liquid Agent: Money Tools for AI Agents API for, with concrete tasks.
★ Agent-run USDC treasury moves through Jentic
An AI agent holding USDC on Base can move funds to the chain where it needs to spend them: it lists open routes, gets a free quote, pays the bridge over x402, and follows the transfer's attestation and mint state by burn transaction. Through Jentic the agent finds each Liquid Agent operation by intent and loads its schema instead of the developer wiring the bridge calls by hand.
List bridge routes, quote a bridge with to=arbitrum and amount=50, pay the bridge over x402, then check the bridge status by its burnTx until the mint completes.
Tokenized stock basket for an agent wallet
An agent can invest idle USDC into a basket of tokenized NVIDIA, Apple, Meta, and Alphabet shares from $1. It previews shares and fee with a quote for a USDC amount, opens its own vault, buys, and later rebalances to target weights or redeems to USDC. Every write returns a transaction for the agent's wallet to sign, so the API never holds the keys.
Get a quote with usdc=10, create a vault, buy into it with 10 USDC, then check the vault by address for its NAV and weights.
Polymarket up/down price feed
Trading agents on Polymarket's crypto up/down markets need the official price to beat. Liquid Agent returns it alongside the live Chainlink price and market prices for BTC, ETH, SOL, and XRP on 5-minute and 15-minute windows, and a start parameter returns a past window's official settle and outcome.
Fetch the Polymarket ETH 15-minute market for the live window and report the price to beat and the current Chainlink price.
Gas sponsorship paid in USDC
Agents that hold only USDC can still transact: the gas sponsor covers gas on Base or Polygon for plain wallets, EntryPoint v0.8 smart accounts, and ERC-7677 smart-wallet SDKs, and a Solana sponsor co-signs a transaction as fee payer, with the fee paid in USDC over x402.
Read the Solana gas sponsor info for the fee payer address, then post a transaction with that sponsor as fee payer and pay the fee in Solana USDC over x402.
37 endpoints — the liquid agent api gives ai agents on-chain money tools paid per call over x402: a one-signature usdc bridge from base to 16 chains, or from arc to base, with free quotes, route lists, and circle cctp transfer status.
METHOD
PATH
DESCRIPTION
/v1/bridge
Bridge USDC with one x402 payment
/v1/bridge/quote
Free quote for a bridge route
/v1/bridge/status/{burnTx}
Bridge attestation and mint state
/v1/basket
Discover the tokenized stock basket
/v1/buy
Buy into a vault with USDC
/v1/vault/{address}
Check a vault's value and weights
/v1/polymarket/btc-5m
Polymarket BTC 5m price to beat
/v1/gas
Sponsor gas paid in USDC
/v1/bridge
Bridge USDC with one x402 payment
/v1/bridge/quote
Free quote for a bridge route
/v1/bridge/status/{burnTx}
Bridge attestation and mint state
/v1/basket
Discover the tokenized stock basket
/v1/buy
Buy into a vault with USDC
/v1/vault/{address}
Check a vault's value and weights
/v1/polymarket/btc-5m
Polymarket BTC 5m price to beat
/v1/gas
Sponsor gas paid in USDC
What agents get from Jentic-routed access to this vendor.
Setup
Wiring Liquid Agent by hand means handling x402 payment challenges on paid routes, an optional SIGN-IN-WITH-X header on free ones, and signing the transactions its basket operations return. Through Jentic you install once, import Liquid Agent from the API Directory, and your agent calls it.
Permission scoping
Liquid Agent carries amounts, recipients, and transaction details in the query string and request body, so rules bound which operations your agent may call, not which wallet or chain. You choose the operations it may call, so money-moving ones like the paid bridge, basket send, or redeem are not included unless you add them.
Credential isolation
If you use a SIGN-IN-WITH-X identity header, it 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 'bridge USDC to Arbitrum' or 'get the Polymarket price to beat', and Jentic returns the matching Liquid Agent operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Alternatives and complements available in the Jentic catalogue.
Specific to using Liquid Agent: Money Tools for AI Agents API through Jentic.
What authentication does the Liquid Agent API use?
Per its OpenAPI spec the Liquid Agent API declares two schemes and no account or API key. Paid operations, such as the bridge, Polymarket prices, signals, and gas sponsorship, use x402: you sign a USDC authorization on Base or Polygon for each call. Free operations, such as quotes, routes, vault reads, and basket writes that return a transaction to sign, accept an optional SIGN-IN-WITH-X header carrying an EIP-4361 wallet identity. The gas sponsor info operations need neither.
Is there a Liquid Agent MCP server?
You don't need an MCP server to give your agent the Liquid Agent API. Jentic connects it directly from the API Directory: import it and your agent discovers the bridge, basket, and Polymarket operations by intent instead of loading a set of tool definitions into its context.
Can I bridge USDC with the Liquid Agent API?
Yes. The bridge operation moves USDC from Base to chains including Arbitrum, OP Mainnet, Polygon, Avalanche, Unichain, and Linea, or from Arc to Base, with one x402 payment. Pass to and amount, the USDC you want to receive with a minimum of 1, and optionally from and a ref referrer address. Use the free quote operation first to see the exact price, then track the transfer with the status operation.
What are the rate limits for the Liquid Agent API?
The OpenAPI spec does not specify rate limits. Paid operations are priced per call through the x402 challenge. Check https://liquidagent.ai for current limits.
Can I limit what my agent is allowed to do with the Liquid Agent API?
Yes. For example, write a rule that allows only the bridge quote, route list, balances, and Polymarket price operations, so the agent can research prices and plan moves while the paid bridge, basket buy, send, and redeem operations stay outside its reach. Every call it makes is logged.
How do I check a vault with the Liquid Agent API through Jentic?
Search Jentic for 'check a tokenized stock vault', load the vault operation, and pass the vault address in the path. It returns the vault's NAV, holdings, current versus target weights, and whether it needs rebalancing. To run it on your own infrastructure, install Jentic One from its GitHub repo.
For Agents
Bridge USDC across chains, buy, rebalance, and redeem a tokenized stock basket, read Polymarket up/down prices to beat, and get gas sponsored in USDC, with payment per call over x402.
Use for: I need to bridge 50 USDC from Base to Arbitrum, Get a free quote for bridging USDC to Polygon, Check whether my CCTP transfer has been minted, Buy 10 dollars of the tokenized stock basket
Not supported: Does not hold custody of funds, place Polymarket trades, or trade individual stocks. Use for USDC bridging, the tokenized stock basket, Polymarket price data, and USDC-paid gas only.
The Liquid Agent API gives AI agents on-chain money tools paid per call over x402: a one-signature USDC bridge from Base to 16 chains, or from Arc to Base, with free quotes, route lists, and Circle CCTP transfer status. It runs a tokenized stock basket of NVIDIA, Apple, Meta, and Alphabet that an agent can buy into from $1, check, rebalance, send to another wallet, or redeem to USDC, with each write returning a transaction for the caller to sign. It also returns the live Polymarket price to beat for BTC, ETH, SOL, and XRP on 5-minute and 15-minute windows, and sponsors gas on Base, Polygon, and Solana in exchange for a USDC fee.
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>