# ACE API Overview
Source: https://docs.chain.link/ace/reference/apis
Last Updated: 2026-10-05

> For the complete documentation index, see [llms.txt](/llms.txt).

ACE exposes three APIs. They share the same host and authentication model, but serve different purposes and use different base paths.

| API                  | Purpose                                                | Access     | Reference                                              |
| -------------------- | ------------------------------------------------------ | ---------- | ------------------------------------------------------ |
| Coordinator API      | Create, update, and delete ACE resources.              | Read-write | [Coordinator API Reference](/api/ace/coordinator/docs) |
| Evaluation API (MVP) | Start and monitor managed offchain policy evaluations. | Read-write | [Evaluation API Reference](/api/ace/evaluation/docs)   |
| Reporting API        | Query onchain state and transaction history.           | Read-only  | [Reporting API Reference](/api/ace/reporting/docs)     |

## Authentication

All API requests require an API key passed in the `Authorization` header. Create your API key in the [Chainlink App](https://app.chain.link) — see [Account Setup](/ace/getting-started/account-setup#3-create-an-api-key) for instructions.

```bash
curl https://ace.api.chain.link/v1/<endpoint> \
  -H "Authorization: Apikey <API_KEY>"
```

> **CAUTION: API key security**
>
> Your API key grants access to the permissions you selected when you created it. Give each key only the permissions it needs, and never share it, commit it to source control, or expose it in client-side code. See [API Keys](/chainlink-platform/api-keys) for the permissions available for ACE.

## Base URLs

The APIs use different base paths on the same host:

| API                  | Base URL                                   |
| -------------------- | ------------------------------------------ |
| Coordinator API      | `https://ace.api.chain.link/v1`            |
| Evaluation API (MVP) | `https://ace.api.chain.link/v1/evaluation` |
| Reporting API        | `https://ace.api.chain.link/v1/reporting`  |

## Coordinator API

The Coordinator API is the management interface for all ACE resources. Everything available in the [Platform UI](https://app.chain.link) is also available through this API.

**Policy Manager operations:**

- Create and manage CRE Connect Wallets
- Deploy and configure PolicyEngine instances
- Create and configure policy instances (from the [Policy Library](/ace/reference/policy-library))
- Register targets and attach policy protections to function selectors
- Manage extractors
- Create and configure [Data Validators](/ace/guides/policy-manager/manage-data-validators) for credential-data checks

**Identity Manager operations:**

- Create and manage identity and credential registries
- Register cross-chain identities (CCIDs) and map wallet addresses
- Define credential types (optionally typed with data schemas) and issue credentials

**Active Monitoring operations:**

- Register monitored tokens and their associated contracts
- Create and archive the monitoring rule of a token
- Add addresses to the watchlist
- Store the TRM API key, set the screening interval, and start or stop screening
- List decisions and read their details

Active Monitoring uses the same host, base URL, and API key as the rest of the Coordinator API. For the endpoints by task, see [Active Monitoring API](/ace/active-monitoring/reference/api).

The Coordinator API also exposes cross-organization access grants (sharing registries and policies), organization settings, and off-chain policy management. For the full schema, parameters, and request/response examples, see the [Coordinator API Reference](/api/ace/coordinator/docs).

## Evaluation API (MVP)

The Evaluation API is the runtime interface for [managed offchain risk policies](/ace/guides/policy-manager/offchain-policies/manage-offchain-policies). An application uses it to:

> **CAUTION: MVP API**
>
> The Evaluation API and managed offchain risk policies are an MVP. Their interfaces and capabilities can change during
> Beta. Contact your Chainlink representative before integrating this API and for help with setup.

- Request a TRM wallet risk evaluation for a specific caller, target, function, chain, and set of permit parameters.
- Receive the deterministic permit ID for that evaluation.
- Poll the evaluation through `evaluating`, `approving`, and a terminal status.
- Submit the protected transaction after the status becomes `ready` and the permit is stored onchain.

For the integration flow, ABI encoding requirements, idempotency, and retry guidance, see [Requesting Offchain Permits](/ace/guides/policy-manager/offchain-policies/request-offchain-permits). For the full schema, see the [Evaluation API Reference](/api/ace/evaluation/docs).

## Reporting API

The Reporting API provides read-only access to onchain state indexed by Chainlink's infrastructure. Use it for audit trails, compliance verification, and monitoring. For a detailed explanation of the data model and indexing pipeline, see [Reporting Manager](/ace/concepts/reporting).

**Queryable resources:**

- **Transactions** — every policy engine evaluation, including the policies that ran, parameters extracted, and outcomes. Filterable by chain, time range, sender, target, function selector, and policy address.
- **Policies** — deployed policy instances and their configuration state at any point in time.
- **Targets** — protected contracts and their full policy wiring (engines, selectors, extractors, policies, defaults).
- **Identities** — identity records, registry memberships, and credentials. Optionally includes full credential details.
- **Permits** — off-chain policy permits delivered on-chain (from off-chain policy evaluation).
- **Registry usage** — registry usage events, for metering and monitoring.

The Policies, Targets, and Identities endpoints accept an `as_of` timestamp for point-in-time historical queries. The Transactions endpoint uses `from`/`to` time range filters.

> **NOTE: API-only reporting**
>
> The Reporting Manager is API-only — there is no reporting UI. See [Beta Scope](/ace/beta-scope) for details.

For the full schema, parameters, and request/response examples, see the [Reporting API Reference](/api/ace/reporting/docs).