VeraDial

VeraDial is an AI receptionist and business phone app for small businesses in the United States and Canada, built by Graham Thomson in Toronto. It gives a business a dedicated US or Canadian number with Vera, an AI receptionist that answers calls and texts 24/7, screens callers, takes messages, books appointments and places outbound AI calls. Developers and agents reach an account three ways - a read-only remote MCP server at api.veradial.com/mcp secured with OAuth 2.1, a Zapier REST Hooks integration API authenticated with vdk_ API keys, and signed HMAC event webhooks for Make, n8n or your own service.

VeraDial is listed with 6 APIs on the APIs.io network, including Hooks API, Keys API, Lines API, and 3 more. Tagged areas include AI Receptionist, Business Phone, Telephony, Voice AI, and SMS.

The VeraDial catalog on APIs.io includes 1 event-driven AsyncAPI specification, 1 JSON-LD context, and 1 Spectral governance ruleset.

VeraDial’s developer surface includes changelog, authentication, documentation, API reference, getting-started guide, support, engineering blog, and 33 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

46.9/100 developing ▼ -11.4 Agent 40/100 agent ready Front door AI 5/6 prominent Heartbeat 69/100 alive Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →

AccessPaid

6 APIs 1 MCP Servers 2 Agent Skills

AI Receptionist Business Phone Telephony Voice AI SMS Webhook MCP Small Business

Kin Score

Kin Score How this is scored →
scored 2026-11-06 · rubric v0.27.0

Composite quality — 46.9/100 · developing

Contract Quality 6.2 / 19

Developer Ergonomics 6.3 / 15

Access Clarity 9.3 / 15

Operational Transparency 3.5 / 10

Contract Governance 3.2 / 9

Discoverability 6.0 / 8

Regulatory Posture 4.8 / 15

Create-or-Update Ergonomics 0.0 / 10

Agent readiness — 40/100 · agent ready

Machine-Readable Contract 18 / 18

Agentic Access Contract 0 / 10

Documented Reversibility 0 / 6

MCP Server 12 / 12

Machine-Readable Auth 10 / 10

Idempotency 9 / 9

Stable Error Semantics 8 / 8

Request/Response Examples 0 / 7

Rate-Limit Signaling 7 / 7

Typed Event Surface 6 / 6

Agent Skills 5 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 0 / 6

Protected Resource Metadata 5 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

Pagination 5 / 5

Distinct Operations 3 / 3

MCP Tool Quality 6 / 6

Regulatory Posture applies to this provider. Its tags matched the Telecommunications regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.

Create-or-Update Ergonomics applies to this provider. This API accepts writes, so it carries 10 points of the composite. It is scored from the published contracts themselves: whether a caller can create-or-update in one call, whether the write accepts a key the caller already holds, and whether the response says which branch ran. Without that, every write needs a search-and-branch in front of it, and the first time that check is skipped a duplicate record is created. Scored against the observed mean rather than raw — a provider at the catalog average is unchanged by this facet, not penalised by it.

The six quality facets above are damped to 75 points between them, because the conditional facet above carries the other 25. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 75% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Show this score on your site.

It updates itself when the score changes. Paste this where you link to your API docs:

<a href="https://apis.io/providers/veradial/"><img src="https://apis.io/badge/veradial/card.svg" alt="VeraDial on APIs.io — Kin Score by API Evangelist"></a>

Other styles, a README pill and a shields.io endpoint are on the badge page.

Raise your score.

Agent readiness — checks not met, largest first (exact, from this profile):

Agentic Access Contract +10 pts — agentic_access artifact present (x-agentic-access), graded by author
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0
Request/Response Examples +7 pts — share of operations carrying request/response examples; else an Examples / Code Samples link
Registration Without a Human +6 pts — a `registration_endpoint` in the served RFC 8414 / OIDC discovery document
Delegated User Identity +6 pts — a served discovery document listing authorization_code in grant_types_supported (served), else an oauth2 authorizationCode flow or openIdConnect declared in an OpenAPI (documented)
Documented Reversibility +6 pts — a reversal operation in the contract, graded up when a window is documented too

4 more unmet checks in the Agent Readiness table above.

Kin Score — facets with the most composite points still available (weight × headroom):

Contract Quality scores 33.2 — up to +16.7 composite points
Developer Ergonomics scores 41.7 — up to +11.7 composite points
Operational Transparency scores 35.5 — up to +8.4 composite points

Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from the provider profile at artifacts.apis.io/veradial/apis.yml: open an issue on github.com/api-evangelist/veradial to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Markets this provider is in provisional

The Kin Score Market layer reads a provider inside its market: its position, and how deep its integrations go. Depth is only comparable within a position. Provisional and unweighted: not part of the Kin Score or agent readiness.

Market	Position	Depth	Registered MCP server	Declares compatibility
Agent Skills (SKILL.md packages)	long-tail	2.5 (thin)	-	1

Registered MCP server and declares compatibility are report only — not weighted. Undeclared means we found nothing we can read, so there is no number: we never infer integrations.

Standards implemented 5

Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.

Model Context Protocol (MCP)

measured — observed by APIs.io (documented)

Agent Skills

measured — observed by APIs.io (published)

OAuth 2.0 Protected Resource Metadata

measured — observed by APIs.io (verified)

OpenAPI

measured — observed by APIs.io (published)

OAuth 2.0

measured — observed by APIs.io (declared)

APIs 6

Individual APIs this provider publishes, each with its own machine-readable definition.

VeraDial MCP Server

Remote, read-only Model Context Protocol server (Streamable HTTP) that lets a customer's own AI assistant - Claude, ChatGPT, Codex or any MCP client - read that customer's VeraD...

VeraDial Hooks API

The Hooks API from VeraDial — 2 operation(s) for hooks.

VeraDial Keys API

The Keys API from VeraDial — 2 operation(s) for keys.

VeraDial Lines API

The Lines API from VeraDial — 1 operation(s) for lines.

VeraDial Me API

The Me API from VeraDial — 1 operation(s) for me.

VeraDial Samples API

The Samples API from VeraDial — 1 operation(s) for samples.

MCP Servers 1

Model Context Protocol servers that expose these APIs to AI agents.

VeraDial MCP Server

Remote MCP server at api.veradial.com over streamable HTTP requiring OAuth; 13 tools listed.

MCP SERVER

Agent Skills 2

Packaged agent skills for driving this provider's APIs from an AI assistant.

veradial-receptionist

AGENT SKILL

veradial-subscribe-to-receptionist-events

AGENT SKILL

VeraDial API pricing

Prices published by VeraDial.

Plan	Price
Vera Lite	$14.99/mo
Vera Plus	$29.99/mo
Vera Business	$59.99/mo
Custom	Quote only

Plan details, limits and sources →

Rate limits

Active Zapier hook subscriptions: A VeraDial account may have up to 25 active Zapier hook subscriptions.
Active API keys: A user may have up to five active keys.

Rate-limit details →

Billed by: subscription · FinOps profile →

Pricing Plans 2

Published pricing tiers and plan structures.

Veradial Plans Pricing

4 plans

PLANS

Veradial Price Estimates

0 plans

PLANS

Rate Limits 1

Documented rate limits and quota policies.

Veradial Rate Limits

2 limits

RATE LIMITS

Service Levels 1

Uptime the provider promises or reports, as SLA4OAI. Read from its own pages; APIs.io runs no monitors.

VeraDial

SLA

FinOps 1

Cost, billing, and metering signals for API financial operations.

Veradial Finops

FINOPS

Event Specifications 1

AsyncAPI definitions for this provider's event-driven and streaming APIs.

Veradial Webhooks

ASYNCAPI

Semantic Vocabularies 1

JSON-LD contexts and semantic vocabularies used across these APIs.

Veradial Context

9 classes · 17 properties

JSON-LD

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs.

VeraDial API Rules

14 rules · 12 errors 1 warnings 1 info

SPECTRAL

JSON Schema 6

Standalone JSON Schema definitions for this provider's data models.

GetKeysResponse

3 properties

JSON SCHEMA

GetLinesResponse

1 properties

JSON SCHEMA

GetSamplesResponse

9 properties

JSON SCHEMA

PostHooksRequest

3 properties

JSON SCHEMA

PostKeysRequest

1 properties

JSON SCHEMA

PostKeysResponse

1 properties

JSON SCHEMA

Security Posture 2

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Veradial Authentication

http-bearer/oauth2 · 4 schemes

SECURITY

Veradial Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Scopes 1

OAuth scopes governing access to this provider's APIs.

Veradial Scopes

3 scopes · authorizationCode

3 scopes

SCOPES

Resources

Get Started 4

Portal, sign-up, and the first successful call

DeveloperPortal

DeveloperPortal

GettingStarted

GettingStarted

SignUp

SignUp

Login

Documentation 2

Reference material describing how the API behaves

Documentation

Documentation

APIReference

APIReference

Agent Surfaces 4

MCP servers, agent skills, and machine-readable catalogs

AgentSkill

LLMsTxt

MCPServer

WellKnown

Design & Contract 10

Pagination, idempotency, versioning, errors, and events

Spectral

JSONLD

Vocabulary

Webhooks

DataModel

Idempotency

Conventions

Lifecycle

ErrorCatalog

Conformance

Scroll for all 10

Build 2

SDKs, sample code, and the tooling you integrate with

ToolCrosswalk

ToolCrosswalk

GitHubOrganization

GitHubOrganization

Access & Security 3

Authentication, authorization, and security posture

Authentication

Authentication

OAuthScopes

OAuthScopes

DomainSecurity

DomainSecurity

Operate 4

Status, limits, changes, and where to get help

RateLimits

ChangeLog

Support

ChangeLog

Commercial 4

Pricing, plans, and the legal terms of use

Plans

Pricing

TermsOfService

PrivacyPolicy

Company 3

The organization behind the API

Website

Website

Blog

Blog

LinkedIn

Other 4

Properties that don't map to a standard resource type

Overlay

Overlay

Hosts

Hosts

Vendors

Vendors

Source (apis.yml)

name: VeraDial
aid: veradial
description: VeraDial is an AI receptionist and business phone app for small businesses in the United States and Canada, built
  by Graham Thomson in Toronto. It gives a business a dedicated US or Canadian number with Vera, an AI receptionist that answers
  calls and texts 24/7, screens callers, takes messages, books appointments and places outbound AI calls. Developers and agents
  reach an account three ways - a read-only remote MCP server at api.veradial.com/mcp secured with OAuth 2.1, a Zapier REST
  Hooks integration API authenticated with vdk_ API keys, and signed HMAC event webhooks for Make, n8n or your own service.
url: https://raw.githubusercontent.com/api-evangelist/veradial/refs/heads/main/apis.yml
accessModel:
  pricing: paid
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Paid
  confidence: high
  source:
  - plans
  - authentication
  - scopes
  - rate-limits
  - security
  generated: '2026-11-06'
  method: derived
image: https://veradial.com/opengraph-image
x-type: company
x-source: apis-io-submission
x-submitted-by: listings@veradial.com, apis.io/add 2026-09-22
x-tier: profiled
x-tier-reason: enrichment pass 2026-09-23 (local-v5; was apis.io/add submission worked by the support sweep 2026-09-23; host
  probed healthy (root 200, invented path 404, llms.txt 200))
specificationVersion: '0.23'
created: '2026-09-23'
modified: '2026-09-23'
tags:
- AI Receptionist
- Business Phone
- Telephony
- Voice AI
- SMS
- Webhook
- MCP
- Small Business
tags_raw:
- AI Receptionist
- Business Phone
- Telephony
- Voice AI
- SMS
- Webhooks
- MCP
- Small Business
common:
- type: RateLimits
  url: rate-limits/veradial-rate-limits.yml
- type: Plans
  url: plans/veradial-plans-pricing.yml
- type: Spectral
  url: rules/veradial-rules.yml
- type: JSONLD
  url: json-ld/veradial-context.jsonld
- type: Vocabulary
  url: vocabulary/veradial-vocabulary.yml
- type: AgentSkill
  url: skills/_index.yml
- type: Webhooks
  url: asyncapi/veradial-webhooks.yml
- type: DataModel
  url: data-model/veradial-data-model.yml
- type: ChangeLog
  url: changelog/veradial-changelog.yml
- type: Idempotency
  url: conventions/veradial-conventions.yml
- type: Conventions
  url: conventions/veradial-conventions.yml
- type: Authentication
  url: authentication/veradial-authentication.yml
- type: OAuthScopes
  url: scopes/veradial-scopes.yml
- type: Lifecycle
  url: lifecycle/veradial-lifecycle.yml
- type: ErrorCatalog
  url: errors/veradial-error-codes.yml
- type: Conformance
  url: conformance/veradial-conformance.yml
- type: Overlay
  url: overlays/veradial-zapier-integration-api-overlay.yaml
- type: LLMsTxt
  url: llms/veradial-llms.txt
- type: ToolCrosswalk
  url: mcp/veradial-tool-crosswalk.yml
- type: MCPServer
  url: mcp/veradial-mcp.yml
- type: WellKnown
  url: well-known/veradial-well-known.yml
- type: Hosts
  url: hosts/veradial-hosts.yml
- type: Vendors
  url: vendors/veradial-vendors.yml
- type: DomainSecurity
  url: security/veradial-domain-security.yml
- type: Website
  url: https://veradial.com/
- type: Documentation
  url: https://veradial.com/help
- type: DeveloperPortal
  url: https://veradial.com/for-agents
- type: APIReference
  url: https://veradial.com/help/zapier-integration-api
- type: GettingStarted
  url: https://veradial.com/help/setup-veradial-first-screened-call
- type: Support
  url: https://veradial.com/faq
- type: Blog
  url: https://veradial.com/blog
- type: ChangeLog
  url: https://veradial.com/updates
- type: Pricing
  url: https://veradial.com/pricing
- type: SignUp
  url: https://app.veradial.com/signup
- type: Login
  url: https://app.veradial.com/
- type: TermsOfService
  url: https://veradial.com/terms
- type: PrivacyPolicy
  url: https://veradial.com/privacy
- type: GitHubOrganization
  url: https://github.com/VeraDial
- type: X
  url: https://x.com/VeraDialApp
- type: LinkedIn
  url: https://www.linkedin.com/company/112327687/
maintainers:
- FN: VeraDial
  email: support@veradial.com
  url: https://veradial.com/
apis:
- name: VeraDial MCP Server
  aid: veradial:mcp
  description: Remote, read-only Model Context Protocol server (Streamable HTTP) that lets a customer's own AI assistant -
    Claude, ChatGPT, Codex or any MCP client - read that customer's VeraDial account - calls with AI screening summaries,
    call and voicemail transcripts, SMS threads, contacts, phone lines, receptionist configuration, plan status and remaining
    minutes. OAuth 2.1 with the customer's VeraDial login; no API keys.
  humanURL: https://veradial.com/for-agents
  baseURL: https://api.veradial.com/mcp
  tags:
  - MCP
  - AI Agents
  - OAuth
  - Read Only
  - Authentication
  tags_raw:
  - MCP
  - AI Agents
  - OAuth
  - Read Only
  - Authentication
  properties:
  - type: Documentation
    url: https://veradial.com/help/connect-ai-assistant
  - type: GettingStarted
    url: https://veradial.com/help/connect-ai-assistant
- aid: veradial:veradial-hooks-api
  name: VeraDial Hooks API
  description: The Hooks API from VeraDial — 2 operation(s) for hooks.
  humanURL: https://veradial.com/for-agents
  baseURL: https://api.veradial.com/mcp
  tags:
  - Hooks
  properties:
  - type: OpenAPI
    url: openapi/veradial-hooks-api-openapi.yml
  - type: APIReference
    url: https://veradial.com/help/zapier-integration-api
  - type: Documentation
    url: https://veradial.com/help/connect-zapier
  - type: Webhooks
    url: https://veradial.com/help/webhooks-make-n8n
  - type: JSONSchema
    url: json-schema/veradial-post-hooks-request-schema.json
  - type: JSONSchema
    url: json-schema/veradial-get-samples-response-schema.json
  - type: JSONSchema
    url: json-schema/veradial-get-lines-response-schema.json
  - type: JSONSchema
    url: json-schema/veradial-post-keys-request-schema.json
  - type: JSONSchema
    url: json-schema/veradial-post-keys-response-schema.json
  - type: JSONSchema
    url: json-schema/veradial-get-keys-response-schema.json
- aid: veradial:veradial-keys-api
  name: VeraDial Keys API
  description: The Keys API from VeraDial — 2 operation(s) for keys.
  humanURL: https://veradial.com/for-agents
  baseURL: https://api.veradial.com/mcp
  tags:
  - Keys
  properties:
  - type: OpenAPI
    url: openapi/veradial-keys-api-openapi.yml
  - type: APIReference
    url: https://veradial.com/help/zapier-integration-api
  - type: Documentation
    url: https://veradial.com/help/connect-zapier
  - type: Webhooks
    url: https://veradial.com/help/webhooks-make-n8n
  - type: JSONSchema
    url: json-schema/veradial-post-hooks-request-schema.json
  - type: JSONSchema
    url: json-schema/veradial-get-samples-response-schema.json
  - type: JSONSchema
    url: json-schema/veradial-get-lines-response-schema.json
  - type: JSONSchema
    url: json-schema/veradial-post-keys-request-schema.json
  - type: JSONSchema
    url: json-schema/veradial-post-keys-response-schema.json
  - type: JSONSchema
    url: json-schema/veradial-get-keys-response-schema.json
- aid: veradial:veradial-lines-api
  name: VeraDial Lines API
  description: The Lines API from VeraDial — 1 operation(s) for lines.
  humanURL: https://veradial.com/for-agents
  baseURL: https://api.veradial.com/mcp
  tags:
  - Lines
  properties:
  - type: OpenAPI
    url: openapi/veradial-lines-api-openapi.yml
  - type: APIReference
    url: https://veradial.com/help/zapier-integration-api
  - type: Documentation
    url: https://veradial.com/help/connect-zapier
  - type: Webhooks
    url: https://veradial.com/help/webhooks-make-n8n
  - type: JSONSchema
    url: json-schema/veradial-post-hooks-request-schema.json
  - type: JSONSchema
    url: json-schema/veradial-get-samples-response-schema.json
  - type: JSONSchema
    url: json-schema/veradial-get-lines-response-schema.json
  - type: JSONSchema
    url: json-schema/veradial-post-keys-request-schema.json
  - type: JSONSchema
    url: json-schema/veradial-post-keys-response-schema.json
  - type: JSONSchema
    url: json-schema/veradial-get-keys-response-schema.json
- aid: veradial:veradial-me-api
  name: VeraDial Me API
  description: The Me API from VeraDial — 1 operation(s) for me.
  humanURL: https://veradial.com/for-agents
  baseURL: https://api.veradial.com/mcp
  tags:
  - Me
  properties:
  - type: OpenAPI
    url: openapi/veradial-me-api-openapi.yml
  - type: APIReference
    url: https://veradial.com/help/zapier-integration-api
  - type: Documentation
    url: https://veradial.com/help/connect-zapier
  - type: Webhooks
    url: https://veradial.com/help/webhooks-make-n8n
  - type: JSONSchema
    url: json-schema/veradial-post-hooks-request-schema.json
  - type: JSONSchema
    url: json-schema/veradial-get-samples-response-schema.json
  - type: JSONSchema
    url: json-schema/veradial-get-lines-response-schema.json
  - type: JSONSchema
    url: json-schema/veradial-post-keys-request-schema.json
  - type: JSONSchema
    url: json-schema/veradial-post-keys-response-schema.json
  - type: JSONSchema
    url: json-schema/veradial-get-keys-response-schema.json
- aid: veradial:veradial-samples-api
  name: VeraDial Samples API
  description: The Samples API from VeraDial — 1 operation(s) for samples.
  humanURL: https://veradial.com/for-agents
  baseURL: https://api.veradial.com/mcp
  tags:
  - Samples
  properties:
  - type: OpenAPI
    url: openapi/veradial-samples-api-openapi.yml
  - type: APIReference
    url: https://veradial.com/help/zapier-integration-api
  - type: Documentation
    url: https://veradial.com/help/connect-zapier
  - type: Webhooks
    url: https://veradial.com/help/webhooks-make-n8n
  - type: JSONSchema
    url: json-schema/veradial-post-hooks-request-schema.json
  - type: JSONSchema
    url: json-schema/veradial-get-samples-response-schema.json
  - type: JSONSchema
    url: json-schema/veradial-get-lines-response-schema.json
  - type: JSONSchema
    url: json-schema/veradial-post-keys-request-schema.json
  - type: JSONSchema
    url: json-schema/veradial-post-keys-response-schema.json
  - type: JSONSchema
    url: json-schema/veradial-get-keys-response-schema.json
x-enrichment:
  date: '2026-09-23'
  status: enriched
  artifacts_added: 36
  pass: local-v5

VeraDial API — frequently asked questions

Does VeraDial have an API?

Yes. APIs.io lists 6 APIs from VeraDial, including VeraDial MCP Server, VeraDial Hooks API and VeraDial Keys API, and 3 more.

Is there an OpenAPI specification for the VeraDial API?

Yes. APIs.io indexes 5 OpenAPI specifications for VeraDial, each linked for download from this page.

How do I authenticate with the VeraDial API?

VeraDial uses bearer-token authentication (http-bearer/oauth2 · 4 schemes). The details are profiled on APIs.io as Veradial Authentication.

How much does the VeraDial API cost?

VeraDial publishes its prices; its Vera Lite plan is $14.99/mo as of 2026-09-23. APIs.io lists 4 pricing plans for VeraDial, with each plan's price, limits and inclusions under Pricing on this page.

Does VeraDial have an MCP server?

Yes. APIs.io lists 1 MCP server for VeraDial: Remote MCP server at api.veradial.com over streamable HTTP requiring OAuth; 13 tools listed.

Is the VeraDial API ready for AI agents?

VeraDial has a Kin Score of 46.9 out of 100 (developing) and an Agent Readiness score of 40.4 (agent-ready), scored by API Evangelist on 2026-11-06.

Work with this as data

Every provider 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 providers

9 MCP tools reach this

find_providersBrowse and filter every provider in the catalog.
get_provider_artifactsEvery artifact this provider publishes, grouped by type.
get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
get_provider_ratingPRO — composite, band, trend and facet scores.
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 provider

curl "https://apis.io/api/v1/providers/veradial"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/veradial/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/veradial/evidence"

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.

GitHub Google LinkedIn

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