WagerX · Authentication Profile

Wagerx Io Authentication

Authentication

WagerX declares 0 security scheme(s) across its OpenAPI definitions.

CompanyGamblingiGamingCasinosRegulatory IntelligenceComplianceCryptocurrencyAgentsMCPA2AResearch
Methods: Schemes: 0 OAuth flows: API key in:

Security Schemes

Source

Authentication Profile

Raw ↑ 
generated: '2026-09-19'
method: searched
source: https://wagerx.io/agent-gateway
docs: https://wagerx.io/agent-gateway
spec_basis: openapi/wagerx-io-openapi.yml declares NO components.securitySchemes and no top-level security — derive-authentication.py therefore produced nothing; this profile is from the provider's docs and discovery documents.
summary: >-
  Entirely anonymous, read-only public access. The Agent Gateway states "No authentication. Rate limit: 30
  requests/minute per IP." and "FREE · NO API KEY"; the agent card declares authentication {publicEndpoints
  true, apiKeyRequired false} with empty securitySchemes/securityRequirements; the OpenAPI has no security
  schemes. The same holds for the MCP endpoints (/mcp, /tech/mcp, /agents/*/mcp — tools/list accepted
  without credentials, answering 200 or a 503 usage circuit, never 401) and the A2A endpoints.
schemes: []
auth_required: false
api_keys:
  issued: false
  signup: none
oauth2: false
oidc: false
mutual_tls: false
integrity:
  note: >-
    Authentication runs in the OTHER direction — the provider signs its answers so a client can verify
    WagerX origin: agent cards carry an ES256 JWS verifiable against https://wagerx.io/.well-known/jwks.json,
    and every A2A/MCP answer wraps data in an Ed25519-signed SignedEvidenceEnvelope verifiable against
    https://wagerx.io/.well-known/wagerx-signing.json (canonicalise data as JSON with sorted keys, compact
    separators, ASCII escaping; verify base64url proof.signature).
  answer_signing_key: https://wagerx.io/.well-known/wagerx-signing.json
  card_signing_jwks: https://wagerx.io/.well-known/jwks.json
abuse_controls:
  rate_limit: 30 requests/minute per IP (see rate-limits/wagerx-io-rate-limits.yml)
  usage_circuit: MCP endpoints return JSON-RPC -32001 / HTTP 503 when the provider's "automatic usage safety circuit" opens (observed 2026-09-19).
  robots: robots.txt explicitly Allows /openapi.json, /llms.txt, the agent cards and the /api/audit/, /api/regulatory-intel, /api/news/latest paths to all agents; Disallows /api/dashboard/, /api/pwa/, /api/kings-live-bets, /chat, /dashboard.

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/wagerx-io-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 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.