Fideo

Fideo Verify & Signals API

Fideo's real-time REST API for identity verification, fraud risk scoring, and identity intelligence. Two endpoints share a common multi-field request schema: POST /verify runs a comprehensive suite of identity and risk checks and returns a 0–1 risk score with per-check results; POST /signals returns modular identity-intelligence bundles (person, email, phone, location, IP, professional, social, and economic signals). Bearer API-key authentication; JSON request and response bodies.

GitHub

Documentation

📖
Documentation
https://docs.fideo.ai
📖
APIReference
https://docs.fideo.ai/docs/verify
📖
GettingStarted
https://docs.fideo.ai/docs/getting-started
📖
Authentication
https://raw.githubusercontent.com/api-evangelist/fideo/refs/heads/main/authentication/fideo-authentication.yml

Other Resources

🔗
Conventions
https://raw.githubusercontent.com/api-evangelist/fideo/refs/heads/main/conventions/fideo-conventions.yml
🔗
ErrorCatalog
https://raw.githubusercontent.com/api-evangelist/fideo/refs/heads/main/errors/fideo-problem-types.yml
🔗
DataModel
https://raw.githubusercontent.com/api-evangelist/fideo/refs/heads/main/data-model/fideo-data-model.yml
🔗
Sandbox
https://raw.githubusercontent.com/api-evangelist/fideo/refs/heads/main/sandbox/fideo-sandbox.yml
🔗
X-MCPServerCandidate
https://raw.githubusercontent.com/api-evangelist/fideo/refs/heads/main/mcp/fideo-mcp.yml
🔗
APIsJSON
https://raw.githubusercontent.com/api-evangelist/fideo/refs/heads/main/apis.yml

Work with this as data

Every API 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 apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • 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 API 
curl "https://apis.io/api/v1/apis/fideo-verify-signals-api"
All apis 
curl "https://apis.io/api/v1/apis?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.

API entry from apis.yml

apis.yml Raw ↑ 
name: Fideo Verify & Signals API
description: 'Fideo''s real-time REST API for identity verification, fraud risk scoring, and identity
  intelligence. Two endpoints share a common multi-field request schema: POST /verify runs a comprehensive
  suite of identity and risk checks and returns a 0–1 risk score with per-check results; POST /signals
  returns modular identity-intelligence bundles (person, email, phone, location, IP, professional, social,
  and economic signals). Bearer API-key authentication; JSON request and response bodies.'
humanURL: https://docs.fideo.ai
baseURL: https://api.fideo.ai
tags:
- Identity Verification
- Fraud Prevention
- Risk Scoring
- Identity Intelligence
properties:
- type: Documentation
  url: https://docs.fideo.ai
- type: APIReference
  url: https://docs.fideo.ai/docs/verify
- type: GettingStarted
  url: https://docs.fideo.ai/docs/getting-started
- type: Authentication
  url: authentication/fideo-authentication.yml
- type: Conventions
  url: conventions/fideo-conventions.yml
- type: ErrorCatalog
  url: errors/fideo-problem-types.yml
- type: DataModel
  url: data-model/fideo-data-model.yml
- type: Sandbox
  url: sandbox/fideo-sandbox.yml
- type: X-MCPServerCandidate
  url: mcp/fideo-mcp.yml
  note: 'Renamed from MCPServer 2026-09-03 (roadmap#247): the manifest self-describes as status: candidate
    — a tool list derived from the published API contracts, not an existing server. The scorer already
    read the manifest and reported mcp_server correctly; the MCPServer type was crediting the artifact-type
    surfaces with a server that does not exist.'