Eagle Virtual API
51
AI ReadinessFoundational (C-)51/100
Official vendor OpenAPI document · agent-readySecurityCompliancebearer9 EndpointsREST
For Agents
Check whether a blockchain wallet has been frozen, seized, or blacklisted by a stablecoin issuer, and read the on-chain enforcement events behind that verdict across the chains the dataset covers.
Use for: Check whether this wallet has been frozen by a stablecoin issuer, Find out why an address was blacklisted on-chain, Get the enforcement history behind a USDC address, Screen a batch of wallet addresses before a payout
Not supported: Does not freeze wallets, move funds, or screen fiat transactions. Use for reading stablecoin enforcement actions against blockchain addresses only.
The Eagle Virtual API reports every recorded action a stablecoin issuer has taken against a blockchain address: blacklistings, freezes, balance seizures, and releases, each tied to the chain, token, issuing company, block, and transaction hash that executed it. A single check returns one wallet's current verdict, one of CLEAR, FROZEN, SEIZED, or UNFROZEN, with the date it applies to and the coverage behind it, while a fuller lookup returns the per-chain coverage and the event history a wallet's public page shows. It also lists every chain it covers with how current each one is, and exposes a monthly feed of every recorded enforcement event.
Install Jentic One Beta
Connect the Eagle Virtual API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Eagle Virtual 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.
1
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%2Feaglevirtual.com%2Feaglevirtual" | sh2
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%2Feaglevirtual.com%2Feaglevirtual" | 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.
Capabilities
What an agent can do with Eagle Virtual API.
Check one wallet's current verdict, CLEAR, FROZEN, SEIZED, or UNFROZEN, with the date it applies to
Read the full enforcement history for an address: blacklistings, freezes, balance seizures, and releases
Trace each enforcement action to its chain, token, issuing company, block, and transaction hash
Screen a batch of wallet addresses in one call before settling a stablecoin transfer
List every blockchain the dataset covers with how current its coverage is
Pull a monthly feed of every recorded enforcement event with the wallet it applies to
Use Cases
Patterns agents use Eagle Virtual API for, with concrete tasks.
★ Agent-driven pre-settlement screening
An AI agent checks a wallet before it moves stablecoins. Through Jentic the agent passes the address to the verdict lookup and reads back CLEAR, FROZEN, SEIZED, or UNFROZEN with the date and coverage behind it, so a transfer to a frozen or seized address is caught before settlement. A batch call screens a whole payout list in one request.
Pass a recipient wallet to the verdict lookup and block the transfer if the result is FROZEN or SEIZED
Compliance audit trail for an address
A compliance workflow needs the evidence behind a flag, not just a yes or no. The address lookup returns the full enforcement history for a wallet, each blacklisting, freeze, balance seizure, and release tied to its chain, issuing company, block, and transaction hash, so an analyst or agent can document exactly which issuer acted, when, and in which transaction.
Fetch the enforcement history for a flagged address and list each action with its issuing company and transaction hash
Monitoring new enforcement events
A monitoring agent watches for fresh activity across the covered chains. The monthly events feed returns every recorded enforcement event with the wallet it applies to, so the agent can detect a newly frozen or seized address among the wallets it tracks and re-check each one's verdict. The chains endpoint reports how current coverage is for each chain.
Read this month's events feed, find any tracked wallet with a new freeze or seizure, and re-check its verdict
Key Endpoints
9 endpoints — the eagle virtual api reports every recorded action a stablecoin issuer has taken against a blockchain address: blacklistings, freezes, balance seizures, and releases, each tied to the chain, token, issuing company, block, and transaction hash that executed it.
METHOD
PATH
DESCRIPTION
GET
/v1/check/{address}
Get the current verdict for one address
GET
/v1/address/{address}
Get per-chain coverage and the enforcement history for a wallet
POST
/v1/addresses/batch
Screen many addresses in one call
GET
/v1/chains
List covered chains with how current each one is
GET
/v1/events/rows
Read the monthly feed of recorded enforcement events
GET
/v1/usage
Check calls made today against the plan's daily limit
GET
/v1/check/{address}
Get the current verdict for one address
GET
/v1/address/{address}
Get per-chain coverage and the enforcement history for a wallet
POST
/v1/addresses/batch
Screen many addresses in one call
GET
/v1/chains
List covered chains with how current each one is
GET
/v1/events/rows
Read the monthly feed of recorded enforcement events
GET
/v1/usage
Check calls made today against the plan's daily limit
Jentic AI Readiness Score
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.
E
Eagle Virtual API
- Foundational (C-)51/100
60
Foundational Compliance67
Developer Experience & Jentic Compatibility29
AI-Readiness & Agent Experience94
Agent Usability60
Security53
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.2
Show dimension breakdown
60
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: C+Signals: 4
96%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
0%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
42%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
67
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: BSignals: 4
1%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
67%
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.
29
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: FSignals: 4
64%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
0%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
53%
Summary Coverage
Coverage of summaries across operations/tags/info.
94
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.
60
Security
Trust, risk posture, and security compliance.
Grade: B-Signals: 1
60%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
53
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: C-Signals: 1
53%
Descriptive Richness
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>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Eagle Virtual API by hand means handling its bearer token, learning its four verdict codes, and deciding when a null verdict means no coverage rather than clear. Through Jentic you install once, import Eagle Virtual from the API Directory, store the token once, and your agent calls it.
Permission scoping
Every Eagle Virtual operation is a read-only lookup, so a rule bounds your agent to the ones it needs: checking a wallet's verdict, reading its enforcement history, and screening a batch. There are no write or delete operations on this API to expose.
Credential isolation
Your Eagle Virtual key is stored once, encrypted, by your own Jentic One instance and injected when a call runs. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'check if a wallet is frozen' or 'read an address's enforcement history', and Jentic returns the matching Eagle Virtual operation with its input schema so the agent calls the right endpoint without reading the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Eagle Virtual API through Jentic.
What authentication does the Eagle Virtual API use?
The Eagle Virtual API authenticates with a bearer token per its OpenAPI spec: you send an account key as `Authorization: Bearer ev_...` on the address and account endpoints. A few endpoints, such as the OpenAPI document itself and the monthly events feed, are reachable without a key. Through Jentic the key is stored encrypted by your own Jentic One instance and injected at call time, so it never enters the agent's context.
Is there an Eagle Virtual MCP server?
You don't need an MCP server to give your agent the Eagle Virtual API. Jentic connects it directly from the API Directory: import it, store your key once, and your agent calls the verdict and history endpoints on demand without loading another server's tool definitions into its context.
Can I check whether a wallet was seized with the Eagle Virtual API?
Yes. A single verdict lookup returns one of CLEAR, FROZEN, SEIZED, or UNFROZEN for an address, with the date it applies to and the coverage behind it, and a fuller lookup returns the matching events with the chain, issuing company, block, and transaction hash. You can also screen many addresses in one batch call before a transfer.
What are the rate limits for the Eagle Virtual API?
The OpenAPI spec does not publish specific rate limits, though it exposes a usage endpoint that reports the calls you have made today against your plan's daily limit. Check the provider's documentation at https://eaglevirtual.com for the limits that apply to your plan.
Can I limit what my agent is allowed to do with the Eagle Virtual API?
Yes. Write a rule that allows only the verdict check and the address history lookups, and your agent can screen wallets and read enforcement events but cannot reach the account usage endpoint. Every call it makes is logged.
How do I screen a wallet with the Eagle Virtual API through Jentic?
Search Jentic for 'check if a wallet has been frozen' and it returns the verdict operation with its input schema; your agent passes an address and reads back the verdict, the date it applies to, and the coverage behind it. To run it on your own infrastructure, install Jentic One from its GitHub repo.
GET STARTED