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.
Limited machine-readable signal and partial portal coverage — documentation a human can read, but little a machine or agent can consume without scraping.
API Evangelist profiles Everclear the way a machine reads it — 19 machine-readable artifacts across 8 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Everclear scores 34.6/100 (thin), with a separate agent-readiness read of 29/100 (agent aware). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-08-17 · rubric v0.11.0
Put this on your own site. The badge is drawn live from Everclear's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/connext/"
title="Everclear on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/connext.svg"
alt="Everclear Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/connext/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/connext/"
title="Everclear on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/connext/card.svg"
alt="Everclear Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>More shapes, themes and sizes → · Score as JSON · How badges work
How we profile Everclear
Each block below is one kind of artifact we hold for Everclear. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 8
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
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 within the panel for all 8 ·
Open Collections 9
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
API Collection
OPEN COLLECTIONChimera Batched Intents API
OPEN COLLECTIONChimera Configs API
OPEN COLLECTIONChimera History API
OPEN COLLECTIONChimera Intents API
OPEN COLLECTIONChimera Invoices API
OPEN COLLECTIONChimera Routes API
OPEN COLLECTIONChimera Solana API
OPEN COLLECTIONChimera Tron API
OPEN COLLECTIONScroll within the panel for all 9 ·
Security Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Resources
Every other property we hold for Everclear — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 2
Portal, sign-up, and the first successful call
Documentation 4
Reference material describing how the API behaves
Agent Surfaces 2
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 5
Pagination, idempotency, versioning, errors, and events
Build 3
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Company 2
The organization behind the API
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/connext · machine-readable index on apis.io
This is an independent, third-party profile of Everclear, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.