# KVdb

**Canonical:** https://apis.io/providers/kvdb/  
**Website:** https://kvdb.io/  
**APIs profiled:** 3

Stop wasting time setting up NoSQL databases. KVdb is a hosted serverless key-value database with a simple HTTPS REST API. Buckets act as namespaces for keys, with built-in access control via secret, read, and write keys, custom Lua scripts, and per-bucket TTLs.

## Kin Score — 27.6 / 100 (thin)

Scored 2026-08-25 under rubric 0.14.0. Trend: flat (+0.0 from 27.6).

| Facet | Score |
|---|---|
| Discoverability | 55.6 |
| Contract Quality | 52.4 |
| Governance | 0.0 |
| Contract Governance | 0.0 |
| Operational Transparency | 7.9 |
| Developer Ergonomics | 23.8 |
| Commercial Clarity | 15.8 |
| Access Clarity | 15.8 |

## Agent readiness — 19.8 (agent-aware)

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

## Access

Freemium · Self-serve signup — onboarding: self-serve, pricing: freemium, trial: no (confidence: high).

## APIs (3)

- **KVdb Buckets API** — Bucket lifecycle operations
- **KVdb Keys API** — Key-value operations within a bucket
- **KVdb Scripts API** — Custom Lua script management and execution

## Agentic access (1)

- **Kvdb Agentic Access** — 10 operations · 7 acting

## Security (2)

- **Kvdb Authentication** — apiKey/http · 2 schemes
- **Kvdb Domain Security** — TLSv1.3 · HSTS · DMARC

## Plans (1)

- **Kvdb Plans Pricing**

## Tags

Databases, Key-Value, NoSQL, Serverless

---

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