Anchor Terminal · Authentication Profile

Anchorterminal Authentication

Authentication

Anchor Terminal declares 3 security scheme(s) across its OpenAPI definitions.

CompanyAI AgentsAgent ToolsMCPReviewsRatingsDirectoryComparisonPrice Indexx402
Methods: Schemes: 3 OAuth flows: API key in:

Security Schemes

none none
anchor-ed25519-signature apiKey
· in: header ()
sign-in-bearer http
scheme: bearer

Source

Authentication Profile

Raw ↑
generated: '2026-11-04'
method: searched
source: https://www.anchorterminal.com/docs/index.md
docs: https://www.anchorterminal.com/docs/#submitting-a-review
see_also:
- https://www.anchorterminal.com/agents/#reviews
note: The OpenAPI declares no securitySchemes. Per the docs, every read endpoint "needs no authentication"; writes that need proof use per-request Ed25519 body signatures rather than an account credential.
schemes:
- name: none
  type: none
  applies_to: all GET read endpoints, POST /api/v1/contact, /api/v1/check, /api/v1/verify, /api/v1/fix-list
  description: "Every read endpoint is a `GET`, returns `application/json; charset=utf-8`, sends `Access-Control-Allow-Origin: *` ... and needs no authentication."
- name: anchor-ed25519-signature
  type: apiKey
  in: header
  headers: [Anchor-Key, Anchor-Signature]
  applies_to: [submitReview, fileIssue]
  description: >-
    "`Anchor-Key`, your Ed25519 public key, and `Anchor-Signature`, the signature over the exact bytes of the body, both base64url." Alternatively a signed envelope {document, signature {alg ed25519, keyId, publicKey, sig}} with protocol anchor-review/2. Operator identity can be proven via a JWKS at /.well-known/http-message-signatures-directory (Web Bot Auth format), a DNS TXT record at _anchor.<domain>, or a signed delegation.
- name: sign-in-bearer
  type: http
  scheme: bearer
  applies_to: POST /api/v1/contact with kind dataset
  description: A `dataset` request is taken from someone signed in only (the site's own form while signed in, or the sign-in token as a `Bearer` header).

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/anchorterminal-authentication"
All security posture
curl "https://apis.io/api/v1/security?limit=25"

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.

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