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 API contracts indexed 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.

The Everclear catalog on APIs.io includes 1 Spectral governance ruleset.

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

🌐 Visit website 📡 Profile data on GitHub

0.0/100 minimal ▬ flat Agent 0/100 human only Front door AI 1/6 silent Heartbeat 11/100 dormant Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →

AccessOpen

1 published contract

Company Blockchain Cryptocurrency Web3 Interoperability Cross-ChainBridgingSettlement Liquidity Intents DeFiChain AbstractionDefunct

Kin Score

Kin Score How this is scored →
scored 2026-11-06 · rubric v0.27.0

Composite quality — 0.0/100 · minimal

Contract Quality 0.0 / 19

Developer Ergonomics 0.0 / 15

Access Clarity 0.0 / 15

Operational Transparency 0.0 / 10

Contract Governance 0.0 / 9

Discoverability 0.0 / 8

Regulatory Posture 2.5 / 15

Create-or-Update Ergonomics 0.0 / 10

Agent readiness — 0/100 · human only

Machine-Readable Contract 18 / 18

Agentic Access Contract 0 / 10

Documented Reversibility 0 / 6

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

Delegated User Identity 0 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

Pagination 5 / 5

Distinct Operations 3 / 3

MCP Tool Quality 6 / 6

Regulatory Posture applies to this provider. Its tags matched the Horizontal (data, software, accessibility, platform) regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.

Create-or-Update Ergonomics applies to this provider. This API accepts writes, so it carries 10 points of the composite. It is scored from the published contracts themselves: whether a caller can create-or-update in one call, whether the write accepts a key the caller already holds, and whether the response says which branch ran. Without that, every write needs a search-and-branch in front of it, and the first time that check is skipped a duplicate record is created. Scored against the observed mean rather than raw — a provider at the catalog average is unchanged by this facet, not penalised by it.

The six quality facets above are damped to 75 points between them, because the conditional facet above carries the other 25. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 75% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Show this score on your site.

It updates itself when the score changes. Paste this where you link to your API docs:

<a href="https://apis.io/providers/connext/"><img src="https://apis.io/badge/connext/card.svg" alt="Everclear on APIs.io — Kin Score by API Evangelist"></a>

Other styles, a README pill and a shields.io endpoint are on the badge page.

Raise your score.

Agent readiness — checks not met, largest first (exact, from this profile):

MCP Server +12 pts — deployment.mode + probe verdict on the mcp/ manifest, not the pointer; an unprobed slug falls back to authorship
Agentic Access Contract +10 pts — agentic_access artifact present (x-agentic-access), graded by author
Idempotency +9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented)
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0
Rate-Limit Signaling +7 pts — OpenAPI responses document X-RateLimit-* / RateLimit headers (verified), else a rate_limits artifact or RateLimits link (documented)
Request/Response Examples +7 pts — share of operations carrying request/response examples; else an Examples / Code Samples link

10 more unmet checks in the Agent Readiness table above.

Kin Score — facets with the most composite points still available (weight × headroom):

Contract Quality scores 0.0 — up to +25.0 composite points
Developer Ergonomics scores 0.0 — up to +20.0 composite points
Access Clarity scores 0.0 — up to +20.0 composite points

Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from the provider profile at artifacts.apis.io/connext/apis.yml: open an issue on github.com/api-evangelist/connext to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Standards implemented 1

Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.

OpenAPI

measured — observed by APIs.io (published)

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 8

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

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 8

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs.

Everclear API Rules

45 rules · 38 errors 1 warnings 6 info

SPECTRAL

OpenAPI Overlays 1

Overlays applied on top of this provider's contracts. Each card says who wrote it: a document the provider publishes, or one API Evangelist derived or generated.

Connext Everclear Overlay

20 actions · documentation · connext-everclear-openapi.yml

DERIVED

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

APIReference

OpenAPI

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

Conventions

DataModel

Lifecycle

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)

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
deliveryModel:
  model: unknown
  open_source: false
  commercial: false
  callable_host: true
  label: Delivery model not determined — needs a product licence on record
  confidence: low
  source:
  - openapi
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: unknown
  onboarding: open
  trial: false
  try_now: false
  public: true
  gated: none
  gated_source:
  - onboarding
  label: Open access
  confidence: low
  source:
  - authentication
  - security
  generated: '2026-11-06'
  method: derived
image: https://raw.githubusercontent.com/everclearorg/brand/main/Everclear-Logo-Black.png
x-type: company
x-source: harvest:secondary-market
specificationVersion: '0.23'
created: '2026-08-09'
modified: '2026-09-15'
x-docs-platform: gitbook
x-docs-platform-confidence: medium
x-docs-platform-checked: 2026-09-24
tags:
- Company
- Blockchain
- Cryptocurrency
- Web3
- Interoperability
- Cross-Chain
- Bridging
- Settlement
- Liquidity
- Intents
- DeFi
- Chain Abstraction
- Defunct
tags_raw:
- 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
  tags_raw:
  - 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
x-status: defunct

Everclear API — frequently asked questions

Does Everclear have an API?

Yes. APIs.io lists 8 APIs from Everclear, including Everclear Batched Intents API, Everclear Configs API and Everclear History API, and 5 more.

Is there an OpenAPI specification for the Everclear API?

Yes. APIs.io indexes 8 OpenAPI specifications for Everclear, each linked for download from this page.

How do I authenticate with the Everclear API?

Everclear uses bearer-token authentication (0 schemes). The details are profiled on APIs.io as Connext Authentication.

Is the Everclear API ready for AI agents?

Everclear has a Kin Score of 0.0 out of 100 (minimal) and an Agent Readiness score of 0.0 (human-only), scored by API Evangelist on 2026-11-06.

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this

find_providersBrowse and filter every provider in the catalog.
get_provider_artifactsEvery artifact this provider publishes, grouped by type.
get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
get_provider_ratingPRO — composite, band, trend and facet scores.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This provider

curl "https://apis.io/api/v1/providers/connext"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/connext/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/connext/evidence"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.