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 publishes 1 API on the APIs.io network: Zapier Integration API. 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.

59.4/100 strong Agent 39/100 agent ready Full breakdown ↓
scored 2026-09-24 · rubric v0.22.0
2 APIs 1 MCP Servers
AI ReceptionistBusiness PhoneTelephonyVoice AISMSWebhookMCPSmall Business

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-09-24 · rubric v0.22.0
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 could not be measured. We hold no machine-readable contract for this provider to read, so there is nothing to measure a write surface against. Excluded rather than scored zero: never-measured and measured-empty are different facts. Publishing an OpenAPI is what makes this facet — and several others — scorable at all.
The six quality facets above are damped to 85 points between them, because the conditional facet above carries the other 15. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 85% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.
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 github.com/api-evangelist/veradial: open an issue to ask a question, or submit a pull request to add artifacts. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

APIs 2

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 Zapier Integration API

REST Hooks integration API used by VeraDial's native Zapier app and documented for direct callers - test a vdk_ API key, list selectable phone lines, fetch event samples, and su...

MCP Servers 1

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

Pricing Plans 1

Published pricing tiers and plan structures.

Rate Limits 1

Documented rate limits and quota policies.

Veradial Rate Limits

2 limits

RATE LIMITS

Event Specifications 1

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

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

Documentation 2

Reference material describing how the API behaves

Agent Surfaces 4

MCP servers, agent skills, and machine-readable catalogs

Design & Contract 10

Pagination, idempotency, versioning, errors, and events

Scroll for all 10

Build 2

SDKs, sample code, and the tooling you integrate with

Access & Security 3

Authentication, authorization, and security posture

Operate 4

Status, limits, changes, and where to get help

Commercial 4

Pricing, plans, and the legal terms of use

Company 3

The organization behind the API

Other 4

Properties that don't map to a standard resource type

Source (apis.yml)

apis.yml Raw ↑
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
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
  - Authentication
  - Read Only
  tags_raw:
  - MCP
  - AI Agents
  - OAuth
  - Read Only
  properties:
  - type: Documentation
    url: https://veradial.com/help/connect-ai-assistant
  - type: GettingStarted
    url: https://veradial.com/help/connect-ai-assistant
- name: VeraDial Zapier Integration API
  aid: veradial:zapier-integration-api
  description: REST Hooks integration API used by VeraDial's native Zapier app and documented for direct callers - test a
    vdk_ API key, list selectable phone lines, fetch event samples, and subscribe or unsubscribe REST Hooks for call.screened,
    voicemail.received, sms.reply_sent and appointment.booked events, plus session-token API-key management routes. OpenAPI
    contract generated from the documentation by API Evangelist (2026-09-23); not the provider's own document.
  humanURL: https://veradial.com/help/zapier-integration-api
  baseURL: https://api.veradial.com/api/v1/integrations/zapier
  tags:
  - REST Hooks
  - Zapier
  - Webhook
  - Integration
  tags_raw:
  - REST Hooks
  - Zapier
  - Webhooks
  - Integrations
  properties:
  - type: OpenAPI
    url: openapi/_ae-authored/veradial-openapi-generated.yml
    x-provenance: generated
  - 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

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"

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.

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