# Bloomsbury

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

Bloomsbury AI was a London-based natural-language-processing startup, backed by Seedcamp, that built Cape — an API making it easy to build software that answers questions about the contents of documents (machine reading / document question answering). Bloomsbury AI was acquired by Facebook in 2018; the hosted Cape API is terminated and bloomsbury.ai now serves only a farewell page. The team open sourced the Cape stack (web services, document QA, machine reader, and clients) under the bloomsburyai GitHub organization, which remains publicly available as archival source. This API Evangelist profile preserves that identity and the open-source footprint.

## Kin Score — 6.8 / 100 (minimal)

Scored 2026-08-21 under rubric 0.12.0. Trend: flat (+0.0 from 6.8).

| Facet | Score |
|---|---|
| Discoverability | 50.0 |
| Contract Quality | 0.0 |
| Governance | 0.0 |
| Contract Governance | 0.0 |
| Operational Transparency | 2.6 |
| Developer Ergonomics | 7.1 |
| Commercial Clarity | 0.0 |
| Access Clarity | 0.0 |

## Agent readiness — 0.0 (human-only)

| Dimension | Value |
|---|---|
| Spec Presence | no |
| Agentic Access | no |
| Reversibility Documented | no |
| MCP Server | no |
| Auth Clarity | no |
| 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 |

## Access

Unknown — onboarding: unknown, pricing: unknown, trial: no (confidence: low).

## Security (1)

- **Bloomsbury Domain Security** — TLSv1.3 · HSTS

## Tags

Company, Artificial Intelligence, Machine-Learning, Natural Language Processing, Question Answering, Machine Reading, Document Processing, Open-Source, Acquired

---

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