Eco · Authentication Profile

Eco Authentication

Authentication

The Eco Routes REST API (quote and intent endpoints) requires NO authentication. There are no securitySchemes declared in the OpenAPI and no API keys, tokens, or OAuth flows. Callers pass a dAppID identifier in the request body purely for attribution. Authorization instead lives at the onchain layer: solver registration/update uses signed requests, and all value movement is executed via EVM/SVM wallet signatures against non-custodial per-intent CREATE2 vault contracts. There is no account or credential provisioning surface.

Eco secures its APIs with none across 0 declared security schemes, as derived from its OpenAPI definitions.

CompanyStablecoinCryptocurrencyPaymentsBlockchainCross-ChainDeFiWeb3InfrastructureFinancial-Services
Methods: none Schemes: 0 OAuth flows: API key in:

Security Schemes

Source

Authentication Profile

Raw ↑ 
generated: '2026-07-19'
method: searched
source: https://docs.eco.com/api-reference/introduction
docs: https://docs.eco.com/api-reference/introduction
summary:
  types: [none]
  api_key_in: []
  oauth2_flows: []
  model: no-auth-with-attribution
description: >-
  The Eco Routes REST API (quote and intent endpoints) requires NO authentication.
  There are no securitySchemes declared in the OpenAPI and no API keys, tokens, or
  OAuth flows. Callers pass a dAppID identifier in the request body purely for
  attribution. Authorization instead lives at the onchain layer: solver
  registration/update uses signed requests, and all value movement is executed via
  EVM/SVM wallet signatures against non-custodial per-intent CREATE2 vault
  contracts. There is no account or credential provisioning surface.
schemes: []
onchain_authorization:
  - mechanism: dAppID
    location: request body
    purpose: attribution only (not access control)
  - mechanism: signed solver requests
    purpose: solver registration and quote submission
  - mechanism: wallet signatures (EVM / SVM)
    purpose: authorizing intent funding and settlement against vault contracts
  - mechanism: Permit3 / Permit2
    purpose: bounded token approvals and gasless intent authorization

Work with this as data

Every security artifact 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 security posture

4 MCP tools reach this
  • find_securityBrowse and filter every security artifact in the catalog.
  • 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 security artifact 
curl "https://apis.io/api/v1/security/eco-authentication"
All security posture 
curl "https://apis.io/api/v1/security?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no email required.

GitHub Google LinkedIn

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