Everclear

Everclear (previously Connext) was a crosschain clearing layer for the intent economy. It netted bidirectional rebalancing flows between solvers, fillers and bridges across chains so that liquidity moved once instead of many times, cutting rebalancing cost by up to 10x. Rebalancers deposited into a Spoke contract on any supported chain and named the destination chains they wanted funds on; a Hub contract on the Everclear clearing chain netted those intents against opposing flow, and any intent that could not be netted became a discounted invoice that arbitrageurs could purchase — a dutch-auction style mechanism that kept the system solvent without a central operator. Everclear shipped a public, unauthenticated REST API ("Chimera API") that read indexed intents, invoices, supported assets, route quotes and settlement history, and that built unsigned EVM, Solana and Tron transactions for callers to sign with their own wallet. On 2026-05-21 the team announced the protocol, the Everclear Foundation and the labs unit had all been wound down; the protocol is sunset, the API host no longer answers, and this profile is an archival record of the developer surface Everclear published.

Everclear publishes 8 APIs on the APIs.io network, including Batched Intents API, Configs API, History API, and 5 more. Tagged areas include Company, Blockchain, Cryptocurrency, Web3, and Interoperability.

Everclear’s developer surface includes documentation, API reference, getting-started guide, support, engineering blog, authentication, and 16 more developer resources.

🌐 Visit website 📡 Source on GitHub
34.6/100 thin ▬ flat Agent 29/100 agent aware Full breakdown ↓
scored 2026-08-17 · rubric v0.11.0
8 APIs
CompanyBlockchainCryptocurrencyWeb3InteroperabilityCross ChainBridgingSettlementLiquidityIntentsDeFiChain AbstractionDefunct

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-08-17 · rubric v0.11.0
Composite quality — 34.6/100 · thin
Contract Quality 12.6 / 25
Developer Ergonomics 11.7 / 20
Commercial Clarity 0.0 / 20
Operational Transparency 0.7 / 13
Governance 1.4 / 12
Discoverability 8.2 / 10
Agent readiness — 29/100 · agent aware
Machine-Readable Contract 18 / 18
Agentic Access Contract 0 / 10
MCP Server 0 / 12
Machine-Readable Auth 10 / 10
Idempotency 0 / 9
Stable Error Semantics 8 / 8
Request/Response Examples 0 / 7
Rate-Limit Signaling 0 / 7
Typed Event Surface 0 / 6
Agent Skills 0 / 5
Well-Known Catalog 0 / 4
Consent & Bot Identity 0 / 3
A2A Agent Card 0 / 8
Dry-Run / Simulate Mode 0 / 4
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. This rating is computed from github.com/api-evangelist/connext: open an issue to ask a question, or submit a pull request to add artifacts. Want it done for you? Prioritized profiling — $2,500 →

APIs 8

Individual APIs this provider publishes, each with its own machine-readable definition.

Everclear Batched Intents API

The Batched Intents API from Everclear — 2 operation(s) for batched intents.

Everclear Configs API

The Configs API from Everclear — 1 operation(s) for configs.

Everclear History API

The History API from Everclear — 1 operation(s) for history.

Everclear Intents API

The Intents API from Everclear — 4 operation(s) for intents.

Everclear Invoices API

The Invoices API from Everclear — 3 operation(s) for invoices.

Everclear Routes API

The Routes API from Everclear — 2 operation(s) for routes.

Everclear Solana API

The Solana API from Everclear — 2 operation(s) for solana.

Everclear Tron API

The Tron API from Everclear — 1 operation(s) for tron.

Scroll for all 8

Open Collections 9

Open, tool-agnostic API collections (OpenAPI-derived and Bruno).

API Collection

OPEN COLLECTION

Chimera Batched Intents API

OPEN COLLECTION

Chimera Configs API

OPEN COLLECTION

Chimera History API

OPEN COLLECTION

Chimera Intents API

OPEN COLLECTION

Chimera Invoices API

OPEN COLLECTION

Chimera Routes API

OPEN COLLECTION

Chimera Solana API

OPEN COLLECTION

Chimera Tron API

OPEN COLLECTION

Scroll for all 9

Security Posture 2

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Connext Authentication

0 schemes

SECURITY

Connext Domain Security

TLSv1.3 · HSTS · DNSSEC · DMARC

SECURITY

Resources

Get Started 2

Portal, sign-up, and the first successful call

DeveloperPortal
DeveloperPortal
 GettingStarted
GettingStarted

Documentation 4

Reference material describing how the API behaves

Documentation
Documentation
 APIReference
APIReference
 OpenAPI
OpenAPI
 GraphQL
GraphQL

Agent Surfaces 2

MCP servers, agent skills, and machine-readable catalogs

LLMsTxt
LLMsTxt
 WellKnown
WellKnown

Design & Contract 5

Pagination, idempotency, versioning, errors, and events

ErrorCatalog
ErrorCatalog
 Conventions
Conventions
 DataModel
DataModel
 Lifecycle
Lifecycle
 Conformance
Conformance

Build 3

SDKs, sample code, and the tooling you integrate with

GitHubOrganization
GitHubOrganization
 Packages
Packages
 SDKs
SDKs

Access & Security 2

Authentication, authorization, and security posture

DomainSecurity
DomainSecurity
 Authentication
Authentication

Operate 1

Status, limits, changes, and where to get help

Support
Support

Company 2

The organization behind the API

Website
Website
 Blog
Blog

Other 1

Properties that don't map to a standard resource type

Overlay
Overlay

Source (apis.yml)

apis.yml Raw ↑ 
aid: connext
name: Everclear
description: Everclear (previously Connext) was a crosschain clearing layer for the intent economy. It netted bidirectional
  rebalancing flows between solvers, fillers and bridges across chains so that liquidity moved once instead of many times,
  cutting rebalancing cost by up to 10x. Rebalancers deposited into a Spoke contract on any supported chain and named the
  destination chains they wanted funds on; a Hub contract on the Everclear clearing chain netted those intents against opposing
  flow, and any intent that could not be netted became a discounted invoice that arbitrageurs could purchase — a dutch-auction
  style mechanism that kept the system solvent without a central operator. Everclear shipped a public, unauthenticated REST
  API ("Chimera API") that read indexed intents, invoices, supported assets, route quotes and settlement history, and that
  built unsigned EVM, Solana and Tron transactions for callers to sign with their own wallet. On 2026-05-21 the team announced
  the protocol, the Everclear Foundation and the labs unit had all been wound down; the protocol is sunset, the API host no
  longer answers, and this profile is an archival record of the developer surface Everclear published.
url: https://raw.githubusercontent.com/api-evangelist/connext/refs/heads/main/apis.yml
image: https://raw.githubusercontent.com/everclearorg/brand/main/Everclear-Logo-Black.png
x-type: company
x-source: harvest:secondary-market
specificationVersion: '0.20'
created: '2026-08-09'
modified: '2026-08-09'
tags:
- Company
- Blockchain
- Cryptocurrency
- Web3
- Interoperability
- Cross Chain
- Bridging
- Settlement
- Liquidity
- Intents
- DeFi
- Chain Abstraction
- Defunct
apis:
- aid: connext:connext-batched-intents-api
  name: Everclear Batched Intents API
  description: The Batched Intents API from Everclear — 2 operation(s) for batched intents.
  humanURL: https://docs.everclear.org/developers/api
  baseURL: https://api.everclear.org
  tags:
  - Batched Intents
  properties:
  - type: OpenAPI
    url: openapi/connext-batched-intents-api-openapi.yml
  - type: Documentation
    url: https://docs.everclear.org/developers/api
  - type: ErrorCatalog
    url: errors/connext-problem-types.yml
  - type: Authentication
    url: authentication/connext-authentication.yml
  - type: Conventions
    url: conventions/connext-conventions.yml
  - type: DataModel
    url: data-model/connext-data-model.yml
- aid: connext:connext-configs-api
  name: Everclear Configs API
  description: The Configs API from Everclear — 1 operation(s) for configs.
  humanURL: https://docs.everclear.org/developers/api
  baseURL: https://api.everclear.org
  tags:
  - Configs
  properties:
  - type: OpenAPI
    url: openapi/connext-configs-api-openapi.yml
  - type: Documentation
    url: https://docs.everclear.org/developers/api
  - type: ErrorCatalog
    url: errors/connext-problem-types.yml
  - type: Authentication
    url: authentication/connext-authentication.yml
  - type: Conventions
    url: conventions/connext-conventions.yml
  - type: DataModel
    url: data-model/connext-data-model.yml
- aid: connext:connext-history-api
  name: Everclear History API
  description: The History API from Everclear — 1 operation(s) for history.
  humanURL: https://docs.everclear.org/developers/api
  baseURL: https://api.everclear.org
  tags:
  - History
  properties:
  - type: OpenAPI
    url: openapi/connext-history-api-openapi.yml
  - type: Documentation
    url: https://docs.everclear.org/developers/api
  - type: ErrorCatalog
    url: errors/connext-problem-types.yml
  - type: Authentication
    url: authentication/connext-authentication.yml
  - type: Conventions
    url: conventions/connext-conventions.yml
  - type: DataModel
    url: data-model/connext-data-model.yml
- aid: connext:connext-intents-api
  name: Everclear Intents API
  description: The Intents API from Everclear — 4 operation(s) for intents.
  humanURL: https://docs.everclear.org/developers/api
  baseURL: https://api.everclear.org
  tags:
  - Intents
  properties:
  - type: OpenAPI
    url: openapi/connext-intents-api-openapi.yml
  - type: Documentation
    url: https://docs.everclear.org/developers/api
  - type: ErrorCatalog
    url: errors/connext-problem-types.yml
  - type: Authentication
    url: authentication/connext-authentication.yml
  - type: Conventions
    url: conventions/connext-conventions.yml
  - type: DataModel
    url: data-model/connext-data-model.yml
- aid: connext:connext-invoices-api
  name: Everclear Invoices API
  description: The Invoices API from Everclear — 3 operation(s) for invoices.
  humanURL: https://docs.everclear.org/developers/api
  baseURL: https://api.everclear.org
  tags:
  - Invoices
  properties:
  - type: OpenAPI
    url: openapi/connext-invoices-api-openapi.yml
  - type: Documentation
    url: https://docs.everclear.org/developers/api
  - type: ErrorCatalog
    url: errors/connext-problem-types.yml
  - type: Authentication
    url: authentication/connext-authentication.yml
  - type: Conventions
    url: conventions/connext-conventions.yml
  - type: DataModel
    url: data-model/connext-data-model.yml
- aid: connext:connext-routes-api
  name: Everclear Routes API
  description: The Routes API from Everclear — 2 operation(s) for routes.
  humanURL: https://docs.everclear.org/developers/api
  baseURL: https://api.everclear.org
  tags:
  - Routes
  properties:
  - type: OpenAPI
    url: openapi/connext-routes-api-openapi.yml
  - type: Documentation
    url: https://docs.everclear.org/developers/api
  - type: ErrorCatalog
    url: errors/connext-problem-types.yml
  - type: Authentication
    url: authentication/connext-authentication.yml
  - type: Conventions
    url: conventions/connext-conventions.yml
  - type: DataModel
    url: data-model/connext-data-model.yml
- aid: connext:connext-solana-api
  name: Everclear Solana API
  description: The Solana API from Everclear — 2 operation(s) for solana.
  humanURL: https://docs.everclear.org/developers/api
  baseURL: https://api.everclear.org
  tags:
  - Solana
  properties:
  - type: OpenAPI
    url: openapi/connext-solana-api-openapi.yml
  - type: Documentation
    url: https://docs.everclear.org/developers/api
  - type: ErrorCatalog
    url: errors/connext-problem-types.yml
  - type: Authentication
    url: authentication/connext-authentication.yml
  - type: Conventions
    url: conventions/connext-conventions.yml
  - type: DataModel
    url: data-model/connext-data-model.yml
- aid: connext:connext-tron-api
  name: Everclear Tron API
  description: The Tron API from Everclear — 1 operation(s) for tron.
  humanURL: https://docs.everclear.org/developers/api
  baseURL: https://api.everclear.org
  tags:
  - Tron
  properties:
  - type: OpenAPI
    url: openapi/connext-tron-api-openapi.yml
  - type: Documentation
    url: https://docs.everclear.org/developers/api
  - type: ErrorCatalog
    url: errors/connext-problem-types.yml
  - type: Authentication
    url: authentication/connext-authentication.yml
  - type: Conventions
    url: conventions/connext-conventions.yml
  - type: DataModel
    url: data-model/connext-data-model.yml
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: DomainSecurity
  url: security/connext-domain-security.yml
- type: Website
  url: https://www.connext.network/
- type: DeveloperPortal
  url: https://docs.everclear.org/
- type: Documentation
  url: https://docs.everclear.org/
- type: APIReference
  url: https://docs.everclear.org/developers/api
- type: GettingStarted
  url: https://docs.everclear.org/developers/getting-started
- type: Support
  url: https://www.connext.network/support
- type: GitHubOrganization
  url: https://github.com/everclearorg
- type: Blog
  url: https://blog.connext.network/
- type: OpenAPI
  url: openapi/_original/connext-everclear-openapi.yml
- type: Overlay
  url: overlays/connext-everclear-overlay.yaml
- type: GraphQL
  url: graphql/connext-everclear-subgraph.graphql
- type: LLMsTxt
  url: llms/connext-llms.txt
- type: Packages
  url: packages/connext-packages.yml
- type: SDKs
  url: packages/connext-packages.yml
- type: WellKnown
  url: well-known/connext-well-known.yml
- type: Authentication
  url: authentication/connext-authentication.yml
- type: ErrorCatalog
  url: errors/connext-problem-types.yml
- type: Conventions
  url: conventions/connext-conventions.yml
- type: DataModel
  url: data-model/connext-data-model.yml
- type: Lifecycle
  url: lifecycle/connext-lifecycle.yml
- type: Conformance
  url: conformance/connext-conformance.yml
x-enrichment:
  date: '2026-08-09'
  status: enriched
  artifacts_added: 13
  pass: local-v1