Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Alice Bridge 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%2Fswaggerhub.valenceapi%2Falice-bridge-api" | 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%2Fswaggerhub.valenceapi%2Falice-bridge-api" | 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 Alice Bridge API.
Validates a signed wallet message
Returns the wallet balance for specified contract
Search for contracts by name or address
Token details for specified contract and token ID
Monitor Alice Bridge API operational status and events
GET STARTED
Patterns agents use Alice Bridge API for, with concrete tasks.
★ Developer Tools Operations
Use the Alice Bridge API to perform developer tools operations programmatically. The API provides 6 endpoints covering core functionality including validates a signed wallet message, returns the wallet balance for specified contract, search for contracts by name or address.
Call POST /wallets/validate to validates a signed wallet message
Automated wallets Management
Automate wallets operations by combining multiple Alice Bridge API endpoints. Agents can returns the wallet balance for specified contract and then search for contracts by name or address in a single workflow.
Call GET /wallets/{walletAddress}/{contractAddress}/balance to returns the wallet balance for specified contract, then verify the result
AI Agent Integration via Jentic
AI agents discover and call Alice Bridge API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle none tokens manually.
Search Jentic for 'validates a signed wallet message', load the operation schema, and execute with Jentic-managed credentials
6 endpoints — swaggerhub.
METHOD
PATH
DESCRIPTION
/wallets/validate
Validates a signed wallet message
/wallets/{walletAddress}/{contractAddress}/balance
Returns the wallet balance for specified contract
/contracts/search
Search for contracts by name or address
/contracts/{contractAddress}
Returns details and metadata for specified contract
/contracts/{contractAddress}/tokens
Returns tokens for specified contract
/contracts/{contractAddress}/tokens/{tokenId}
Token details for specified contract and token ID
/wallets/validate
Validates a signed wallet message
/wallets/{walletAddress}/{contractAddress}/balance
Returns the wallet balance for specified contract
/contracts/search
Search for contracts by name or address
/contracts/{contractAddress}
Returns details and metadata for specified contract
/contracts/{contractAddress}/tokens
Returns tokens for specified contract
/contracts/{contractAddress}/tokens/{tokenId}
Token details for specified contract and token ID
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Alice Bridge API by hand means standing up its AWS us-east-1 endpoint, handling its open (no-auth) access, and coding wallet and contract lookups against its execute-api host yourself. Through Jentic you install once, import the Alice Bridge API from the API Directory, store any needed config once, and your agent calls it.
Permission scoping
The Alice Bridge API puts the wallet and contract in the URL path (/wallets/{walletAddress}/{contractAddress}/balance and /contracts/{contractAddress}/...), so a rule can pin your agent to one contract address: it can read that contract and its tokens and nothing else. You choose the operations it may call, so validation or broader contract search is not included unless you add them.
Credential isolation
This API requires no credential, and any config your setup needs 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 'validate a signed wallet message' or 'get a token balance for a wallet', and Jentic returns the matching Alice Bridge API 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.
Github
Alternative developer tools API
Choose Github when you need a different approach to developer tools operations
Specific to using Alice Bridge API through Jentic.
What authentication does the Alice Bridge API use?
The Alice Bridge API uses no authentication. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.
Can I validates a signed wallet message with the Alice Bridge API?
Yes. Use the POST /wallets/validate endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the Alice Bridge API?
Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.
How do I validates a signed wallet message through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'validates a signed wallet message'. Jentic returns the matching Alice Bridge API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the Alice Bridge API have?
The Alice Bridge API exposes 6 endpoints covering wallets, contracts operations.
Can I limit what my agent is allowed to do with the Alice Bridge API?
Yes. Because you run Jentic One yourself, your own rules decide which Alice Bridge API operations and credentials your agent may use. Since this API puts the wallet and contract in the URL path, such as GET /wallets/{walletAddress}/{contractAddress}/balance and GET /contracts/{contractAddress}/tokens, you can pin your agent to a single contract address so it only reads that contract and its tokens. You also choose the exact operations it may call, so message validation via POST /wallets/validate or broad contract search stays off unless you enable it.
Know of an official OpenAPI document? Contribute it →
For Agents
Programmatically validates a signed wallet message, returns the wallet balance for specified contract. Covers 6 operations.
Use for: I need to validates a signed wallet message, I want to returns the wallet balance for specified contract, Search for for contracts by name or address, Find all returns details and metadata for specified contract
Not supported: Does not handle payments, communications, or crm - use for developer tools only.
swaggerhub.valenceapi/alicebridge version 1.0.0. The API exposes 6 endpoints.