# SecondFactor

**Canonical:** https://apis.io/providers/secondfactor/  
**Website:** https://secondfactor.ai  
**APIs profiled:** 0

SecondFactor provides an OTP Delivery & Verification API that enables developers to send one‑time passwords via SMS, WhatsApp, Viber, and RCS. The platform intelligently routes messages to the lowest‑cost channel, offers automatic fallback, delivery logs, template management, and a pricing calculator. It aims to reduce authentication costs and improve user experience with a single, multi‑channel API. Documentation, pricing, and support are available online, and the service is trusted by global companies for secure, fast, and affordable OTP delivery.

## Kin Score — 34.7 / 100 (thin)

Scored 2026-10-31 under rubric 0.25.0.

| Facet | Score |
|---|---|
| Discoverability | 48.2 |
| Contract Quality | 39.0 |
| Contract Governance | 0.0 |
| Operational Transparency | 7.9 |
| Developer Ergonomics | 47.6 |
| Access Clarity | 44.7 |

Regulatory layer — **Horizontal (data, software, accessibility, platform)**: 19.6 (matched via fallback).

## Agent readiness — 28.6 (agent-ready)

| Dimension | Value |
|---|---|
| Spec Presence | yes |
| Agentic Access | no |
| Reversibility Documented | no |
| MCP Server | documented |
| Auth Clarity | bearer |
| Idempotency | no |
| Error Semantics | documented |
| OpenAPI Examples | no |
| Rate Limit Signal | no |
| Event Surface Described | yes |
| Agent Skills | no |
| Well Known Catalog | yes |
| Consent Identity | no |
| Agent Card | no |
| Dry Run Mode | no |
| Delegated Identity | no |
| Protected Resource Metadata | no |
| Dynamic Client Registration | no |
| Agentic Commerce | no |
| Pagination Ratio | na |
| Operation Distinctiveness | na |

## Security (2)

- **Secondfactor Authentication** — 1 scheme
- **Secondfactor Domain Security** — TLSv1.3 · DMARC

## Tags

Company, OTP, Authentication, Multi-Channel, Messaging

---

Profiled by [API Evangelist](https://apievangelist.com) and published on [APIs.io](https://apis.io/providers/secondfactor/). Scores are computed from the provider's own public artifacts under a published rubric.