ACE API Overview

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

APIPurposeAccessReference
Coordinator APICreate, update, and delete ACE resources.Read-writeCoordinator API Reference
Evaluation API (MVP)Start and monitor managed offchain policy evaluations.Read-writeEvaluation API Reference
Reporting APIQuery onchain state and transaction history.Read-onlyReporting API Reference

Authentication

All API requests require an API key passed in the Authorization header. Create your API key in the Chainlink App — see Account Setup for instructions.

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

Base URLs

The APIs use different base paths on the same host:

APIBase URL
Coordinator APIhttps://ace.api.chain.link/v1
Evaluation API (MVP)https://ace.api.chain.link/v1/evaluation
Reporting APIhttps://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 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)
  • Register targets and attach policy protections to function selectors
  • Manage extractors
  • Create and configure 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

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.

Evaluation API (MVP)

The Evaluation API is the runtime interface for managed offchain risk policies. An application uses it to:

  • 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. For the full schema, see the Evaluation API Reference.

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.

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.

For the full schema, parameters, and request/response examples, see the Reporting API Reference.

Get the latest Chainlink content straight to your inbox.