canonical: https://jentic.com/apis/eaglevirtual.com/eaglevirtual

# Eagle Virtual API

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.

## For AI 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.

## Scope

Does not freeze wallets, move funds, or screen fiat transactions. Use for reading stablecoin enforcement actions against blockchain addresses only.

## Capabilities

- 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

### 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.

Example prompt: 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.

Example prompt: 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.

Example prompt: Read this month's events feed, find any tracked wallet with a new freeze or seizure, and re-check its verdict

## Key endpoints

| 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 |

## Key resources

- **Address verdict** — The current verdict for one wallet, with the date it applies to and the coverage behind it
- **Address detail** — Per-chain coverage and the full enforcement event history for a wallet
- **Chains** — Every blockchain covered, with lane status and how current each one is
- **Events** — A monthly feed of every recorded enforcement event with its wallet
- **Usage** — Calls made today against the plan's daily limit

## AI readiness

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.

- **Score:** 51 / 100
- **Maturity:** Foundational
- **Dimensions:**
  - Foundational Compliance: 60 / 100
  - Developer Experience & Jentic Compatibility: 67 / 100
  - AI-Readiness & Agent Experience: 29 / 100
  - Agent Usability: 94 / 100
  - Security: 60 / 100
  - AI Discoverability: 53 / 100
- **View full report:** https://jentic.com/apis/eaglevirtual.com/eaglevirtual/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **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 handling:** 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.
- **Discovery method:** 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

- **Bitquery** — Queries on-chain activity and transfers across many chains via GraphQL
- **Alchemy** — Reads raw transactions and balances for the same addresses this API screens
- **Moralis EVM API** — Returns wallet balances and token transfers across EVM chains

## FAQ

### 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.