# Numerify

**Canonical:** https://apis.io/providers/numerify-com/  
**Website:** https://numerify.com  
**APIs profiled:** 0

Numerify is a venture-backed startup originally listed in the API Evangelist harvest backlog, identified as a portfolio company of Lightspeed Venture Partners. The company appears to have been acquired or rebranded, as its primary domain numerify.com now redirects to Digital.ai, a separate enterprise software platform. No dedicated website or API documentation for Numerify could be located, and no public API specifications were found. This profile records the limited publicly available information about Numerify, noting its acquisition status and lack of active endpoints.

## Kin Score — 15.3 / 100 (emerging)

Scored 2026-10-31 under rubric 0.25.0.

| Facet | Score |
|---|---|
| Discoverability | 50.0 |
| Contract Quality | 0.0 |
| Contract Governance | 0.0 |
| Operational Transparency | 0.0 |
| Developer Ergonomics | 40.5 |
| Access Clarity | 10.5 |

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

## Agent readiness — 17.5 (agent-aware)

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

## Security (2)

- **Numerify Com Authentication** — 3 schemes
- **Numerify Com Domain Security** — TLSv1.2

## Tags

Company, Venture, Startup, Acquired, API

---

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