Veritus

Veritus (Veritus Agent) is a San Francisco fintech (Y Combinator S2025) building compliant, voice-first AI agents for the consumer-lending lifecycle - origination, servicing, and collections. Its omnichannel platform places AI voice calls, SMS, and email to borrowers, running every contact through a built-in compliance engine (respectful hours, frequency limits, cease-and-desist, model-validation notices) before outreach. The REST API (OpenAPI 3.1, bearer auth, isolated sandbox and production environments, HMAC-signed webhooks) lets lenders, servicers, and collections agencies create customers, place compliance-checked calls, run omnichannel drip campaigns, import and analyze SMS/email interactions, and retrieve call recordings.

Veritus publishes 5 API contracts indexed on the APIs.io network, including Calls API, Clients API, Customers API, and 2 more. Tagged areas include Company, Fintech, Consumer Lending, Collection, and AI Agents.

The Veritus catalog on APIs.io includes 1 event-driven AsyncAPI specification and 1 Spectral governance ruleset.

Veritus’ developer surface includes engineering blog, documentation, signup flow, authentication, and 17 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

52.2/100 developing ▬ flat Agent 30/100 agent ready Front door AI 6/6 dominant saas Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →

1 published contract 3 Agent Skills

Company Fintech Consumer Lending Collection AI Agents Voice AI Communications Compliance Debt Collection

What this lets a business do 1

Business capabilities this provider's published APIs can perform, derived from its own contracts. Browse all capabilities →

Application Communications

AE-150

Calls

POST /calls/bulk

Kin Score

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

Composite quality — 52.2/100 · developing

Contract Quality 10.9 / 19

Developer Ergonomics 9.2 / 15

Access Clarity 7.5 / 15

Operational Transparency 1.5 / 10

Contract Governance 1.6 / 9

Discoverability 5.5 / 8

Regulatory Posture 4.4 / 15

Create-or-Update Ergonomics 2.8 / 10

Agent readiness — 30/100 · agent ready

Machine-Readable Contract 18 / 18

Agentic Access Contract 0 / 10

Documented Reversibility 0 / 6

MCP Server 0 / 12

Machine-Readable Auth 10 / 10

Idempotency 9 / 9

Stable Error Semantics 8 / 8

Request/Response Examples 7 / 7

Rate-Limit Signaling 0 / 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 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

Pagination 0 / 5

Distinct Operations 3 / 3

MCP Tool Quality 6 / 6

Regulatory Posture applies to this provider. Its tags matched the AI & Biometrics 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/veritus/"><img src="https://apis.io/badge/veritus/card.svg" alt="Veritus 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):

MCP Server +12 pts — deployment.mode + probe verdict on the mcp/ manifest, not the pointer; an unprobed slug falls back to authorship
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
Rate-Limit Signaling +7 pts — OpenAPI responses document X-RateLimit-* / RateLimit headers (verified), else a rate_limits artifact or RateLimits link (documented)
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)

7 more unmet checks in the Agent Readiness table above.

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

Operational Transparency scores 15.8 — up to +10.9 composite points
Contract Quality scores 58.2 — up to +10.5 composite points
Access Clarity scores 50.0 — up to +10.0 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/veritus/apis.yml: open an issue on github.com/api-evangelist/veritus 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
Consumer Lending Licensing (UK, US, Canada credit licence registers)	undeclared	-	-	-

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 1

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.

OpenAPI

measured — observed by APIs.io (published)

APIs 5

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

Veritus Calls API

The Calls API from Veritus — 2 operation(s) for calls.

Veritus Clients API

The Clients API from Veritus — 1 operation(s) for clients.

Veritus Customers API

The Customers API from Veritus — 12 operation(s) for customers.

Veritus Interactions API

The Interactions API from Veritus — 1 operation(s) for interactions.

Veritus API

The Veritus API API from Veritus — 0 operation(s) for veritus api.

Open Collections 4

Open, tool-agnostic API collections (OpenAPI-derived and Bruno).

Veritus Calls API

OPEN COLLECTION

Veritus Calls Clients API

OPEN COLLECTION

Veritus Calls Customers API

OPEN COLLECTION

Veritus Calls Interactions API

OPEN COLLECTION

Agent Skills 3

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

veritus-drip-campaign

AGENT SKILL

veritus-import-analyze-interaction

AGENT SKILL

veritus-outbound-call

AGENT SKILL

Event Specifications 1

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

Veritus Agent Webhooks

Outbound webhooks Veritus Agent POSTs to a subscriber-supplied URL when calls complete or drip-campaign events occur. Payloads are signed with HMAC SHA-256. Register a webhook b...

ASYNCAPI

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs.

Veritus API Rules

58 rules · 48 errors 6 warnings 4 info

SPECTRAL

OpenAPI Overlays 1

Overlays applied on top of this provider's contracts. Each card says who wrote it: a document the provider publishes, or one API Evangelist derived or generated.

Veritus Openapi Overlay

19 actions · documentation · veritus-openapi.json

DERIVED

Security Posture 3

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

Veritus Authentication

http · 1 scheme

SECURITY

Veritus Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Veritus Trust Center

SOC 2 Type 2, ISO 27001, PCI DSS, HIPAA, EU AI Act

SECURITY

Resources

Get Started 3

Portal, sign-up, and the first successful call

DeveloperPortal

DeveloperPortal

SignUp

SignUp

Login

Documentation 2

Reference material describing how the API behaves

Documentation

Documentation

AsyncAPI

AsyncAPI

Agent Surfaces 2

MCP servers, agent skills, and machine-readable catalogs

X-MCPServerCandidate

X-MCPServerCandidate

AgentSkill

AgentSkill

Design & Contract 2

Pagination, idempotency, versioning, errors, and events

Idempotency

Idempotency

Webhooks

Webhooks

Access & Security 4

Authentication, authorization, and security posture

Authentication

TrustCenter

Compliance

DomainSecurity

Operate 1

Status, limits, changes, and where to get help

StatusPage

StatusPage

Commercial 2

Pricing, plans, and the legal terms of use

TermsOfService

TermsOfService

PrivacyPolicy

PrivacyPolicy

Company 3

The organization behind the API

Blog

Blog

Website

Website

LinkedIn

Other 2

Properties that don't map to a standard resource type

CapabilityMap

CapabilityMap

Overlay

Overlay

Source (apis.yml)

aid: veritus
name: Veritus
description: Veritus (Veritus Agent) is a San Francisco fintech (Y Combinator S2025) building compliant, voice-first AI agents
  for the consumer-lending lifecycle - origination, servicing, and collections. Its omnichannel platform places AI voice calls,
  SMS, and email to borrowers, running every contact through a built-in compliance engine (respectful hours, frequency limits,
  cease-and-desist, model-validation notices) before outreach. The REST API (OpenAPI 3.1, bearer auth, isolated sandbox and
  production environments, HMAC-signed webhooks) lets lenders, servicers, and collections agencies create customers, place
  compliance-checked calls, run omnichannel drip campaigns, import and analyze SMS/email interactions, and retrieve call recordings.
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: true
  label: Hosted service · you call their endpoint
  confidence: high
  source:
  - openapi
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: unknown
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Unknown
  confidence: low
  source:
  - authentication
  - security
  - sandbox
  generated: '2026-11-06'
  method: derived
image: https://veritus.com/apple-touch-icon.png
url: https://raw.githubusercontent.com/api-evangelist/veritus/refs/heads/main/apis.yml
x-type: company
x-source: vc-portfolio
x-backed-by:
- threshold-ventures
x-tier: stub
x-tier-reason: portfolio-lead
specificationVersion: '0.23'
created: '2026-07-17'
modified: '2026-10-06'
x-docs-platform: mintlify
x-docs-platform-confidence: medium
x-docs-platform-checked: 2026-10-17
tags:
- Company
- Fintech
- Consumer Lending
- Collection
- AI Agents
- Voice AI
- Communications
- Compliance
- Debt Collection
tags_raw:
- Company
- Fintech
- Consumer Lending
- Collections
- AI Agents
- Voice AI
- Communications
- Compliance
- Debt Collection
apis:
- aid: veritus:veritus-calls-api
  name: Veritus Calls API
  description: The Calls API from Veritus — 2 operation(s) for calls.
  humanURL: https://docs.veritus.com/
  baseURL: https://app.veritus.com/api/v1
  tags:
  - Calls
  properties:
  - type: OpenAPI
    url: openapi/veritus-calls-api-openapi.yml
  - type: Documentation
    url: https://docs.veritus.com/
  - type: APIReference
    url: https://docs.veritus.com/api-reference/customers/post
  - type: GettingStarted
    url: https://docs.veritus.com/
  - type: LLMsTxt
    url: llms/veritus-llms.txt
  - type: ErrorCatalog
    url: errors/veritus-problem-types.yml
  - type: Conventions
    url: conventions/veritus-conventions.yml
  - type: Sandbox
    url: sandbox/veritus-sandbox.yml
  - type: Conformance
    url: conformance/veritus-conformance.yml
  - type: Lifecycle
    url: lifecycle/veritus-lifecycle.yml
  - type: DataModel
    url: data-model/veritus-data-model.yml
- aid: veritus:veritus-clients-api
  name: Veritus Clients API
  description: The Clients API from Veritus — 1 operation(s) for clients.
  humanURL: https://docs.veritus.com/
  baseURL: https://app.veritus.com/api/v1
  tags:
  - Clients
  properties:
  - type: OpenAPI
    url: openapi/veritus-clients-api-openapi.yml
  - type: Documentation
    url: https://docs.veritus.com/
  - type: APIReference
    url: https://docs.veritus.com/api-reference/customers/post
  - type: GettingStarted
    url: https://docs.veritus.com/
  - type: LLMsTxt
    url: llms/veritus-llms.txt
  - type: ErrorCatalog
    url: errors/veritus-problem-types.yml
  - type: Conventions
    url: conventions/veritus-conventions.yml
  - type: Sandbox
    url: sandbox/veritus-sandbox.yml
  - type: Conformance
    url: conformance/veritus-conformance.yml
  - type: Lifecycle
    url: lifecycle/veritus-lifecycle.yml
  - type: DataModel
    url: data-model/veritus-data-model.yml
- aid: veritus:veritus-customers-api
  name: Veritus Customers API
  description: The Customers API from Veritus — 12 operation(s) for customers.
  humanURL: https://docs.veritus.com/
  baseURL: https://app.veritus.com/api/v1
  tags:
  - Customers
  properties:
  - type: OpenAPI
    url: openapi/veritus-customers-api-openapi.yml
  - type: Documentation
    url: https://docs.veritus.com/
  - type: APIReference
    url: https://docs.veritus.com/api-reference/customers/post
  - type: GettingStarted
    url: https://docs.veritus.com/
  - type: LLMsTxt
    url: llms/veritus-llms.txt
  - type: ErrorCatalog
    url: errors/veritus-problem-types.yml
  - type: Conventions
    url: conventions/veritus-conventions.yml
  - type: Sandbox
    url: sandbox/veritus-sandbox.yml
  - type: Conformance
    url: conformance/veritus-conformance.yml
  - type: Lifecycle
    url: lifecycle/veritus-lifecycle.yml
  - type: DataModel
    url: data-model/veritus-data-model.yml
- aid: veritus:veritus-interactions-api
  name: Veritus Interactions API
  description: The Interactions API from Veritus — 1 operation(s) for interactions.
  humanURL: https://docs.veritus.com/
  baseURL: https://app.veritus.com/api/v1
  tags:
  - Interactions
  properties:
  - type: OpenAPI
    url: openapi/veritus-interactions-api-openapi.yml
  - type: Documentation
    url: https://docs.veritus.com/
  - type: APIReference
    url: https://docs.veritus.com/api-reference/customers/post
  - type: GettingStarted
    url: https://docs.veritus.com/
  - type: LLMsTxt
    url: llms/veritus-llms.txt
  - type: ErrorCatalog
    url: errors/veritus-problem-types.yml
  - type: Conventions
    url: conventions/veritus-conventions.yml
  - type: Sandbox
    url: sandbox/veritus-sandbox.yml
  - type: Conformance
    url: conformance/veritus-conformance.yml
  - type: Lifecycle
    url: lifecycle/veritus-lifecycle.yml
  - type: DataModel
    url: data-model/veritus-data-model.yml
- aid: veritus:veritus-veritus-api-api
  name: Veritus API
  description: The Veritus API API from Veritus — 0 operation(s) for veritus api.
  humanURL: https://docs.veritus.com/
  baseURL: https://app.veritus.com/api/v1
  tags:
  - Veritus API
  properties:
  - type: OpenAPI
    url: openapi/veritus-veritus-api-api-openapi.yml
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: CapabilityMap
  url: capabilities/veritus-capability-edges.yml
  name: Veritus Business Capability Map
- url: https://veritus.com/insights/
  type: Blog
- type: X-MCPServerCandidate
  url: mcp/veritus-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.'
- type: Overlay
  url: overlays/veritus-openapi-overlay.yaml
- type: Website
  url: https://veritus.com/
- type: DeveloperPortal
  url: https://docs.veritus.com/
- type: Documentation
  url: https://docs.veritus.com/
- type: SignUp
  url: https://app.veritus.com/try
- type: Login
  url: https://app.veritus.com
- type: TermsOfService
  url: https://veritus.com/terms
- type: PrivacyPolicy
  url: https://veritus.com/privacy
- type: LinkedIn
  url: https://www.linkedin.com/company/veritus-agent
- type: Authentication
  url: authentication/veritus-authentication.yml
- type: Idempotency
  url: conventions/veritus-conventions.yml
- type: StatusPage
  url: https://status.veritus.com/
- type: AsyncAPI
  url: asyncapi/veritus-webhooks-asyncapi.yml
- type: Webhooks
  url: asyncapi/veritus-webhooks-asyncapi.yml
- type: AgentSkill
  url: skills/_index.yml
- type: TrustCenter
  url: security/veritus-trust-center.yml
- type: Compliance
  url: security/veritus-trust-center.yml
- type: DomainSecurity
  url: security/veritus-domain-security.yml
x-enrichment:
  date: '2026-07-21'
  status: enriched
  artifacts_added: 19
  pass: local-v1

Veritus API — frequently asked questions

Does Veritus have an API?

Yes. APIs.io lists 5 APIs from Veritus, including Veritus Calls API, Veritus Clients API and Veritus Customers API, and 2 more.

Is there an OpenAPI specification for the Veritus API?

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

How do I authenticate with the Veritus API?

Veritus uses bearer-token authentication (http · 1 scheme). The details are profiled on APIs.io as Veritus Authentication.

Is the Veritus API ready for AI agents?

Veritus has a Kin Score of 52.2 out of 100 (developing) and an Agent Readiness score of 30.1 (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/veritus"

All providers

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

Every operation they expose

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

How their score was established

curl "https://apis.io/api/v1/providers/veritus/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.