# InfoLang Inc. Correspondences API

**Canonical:** https://apis.io/apis/infolang-ai/infolang-ai-correspondences-api/  
**Provider:** InfoLang Inc. — https://apis.io/providers/infolang-ai/  
**Base URL:** https://api.infolang.ai  
**Documentation:** https://docs.infolang.ai/api-reference

InfoLang Inc. Correspondences API is one of 22 APIs that [InfoLang Inc.](https://apis.io/providers/infolang-ai/) publishes on the [APIs.io](https://apis.io/) network, described by a machine-readable OpenAPI specification. Tagged areas include Correspondences. The published artifact set on APIs.io includes an OpenAPI specification.

WHETHER TWO KEYS NAME ONE FACT — `il-correspondence` pointed at Phase 1's subject keys. Subject-key drift (two agents writing `fact:convoy-departure` and `fact:convoy-departs`) silently splits one fact into two folds with nothing looking wrong; this surface makes the split visible and repairable WITHOUT rewriting a log. The gateway can PROPOSE that two keys correspond; only an operator credential can `identify` them as one thing, and even that is forward-only. Recall can annotate every subjected hit (`correspondence: true`) with a `split_risk` flag — and never unions the two subjects' beliefs. All three lanes, gated on `coord:read` / `coord:write`; `501` where the upstream kernel verbs are not compiled in.

## Operations (6)

| Method | Path | Summary |
|---|---|---|
| POST | `/v2/workspaces/{id}/correspondences` | Propose a link between two keys |
| POST | `/v2/workspaces/{id}/correspondences/{link}/bottom` | Withdraw a proposal |
| POST | `/v2/workspaces/{id}/correspondence/identify` | Declare two keys to be one thing (operator only) |
| POST | `/v2/workspaces/{id}/correspondence/unidentify` | Unsay an identity (operator only) |
| GET | `/v2/workspaces/{id}/correspondence` | The operator queue: what is proposed, disputed, and ruled |
| GET | `/v2/workspaces/{id}/memories/{memoryId}/correspondence` | What else might name this memory's fact |

## Machine-readable artifacts (1)

- **OpenAPI** — https://artifacts.apis.io/infolang-ai/openapi/infolang-ai-correspondences-api-openapi.yml

## Other InfoLang Inc. APIs (12)

- [InfoLang Inc. Activity API](https://apis.io/apis/infolang-ai/infolang-ai-activity-api/)
- [InfoLang Inc. Billing API](https://apis.io/apis/infolang-ai/infolang-ai-billing-api/)
- [InfoLang Inc. Canon API](https://apis.io/apis/infolang-ai/infolang-ai-canon-api/)
- [InfoLang Inc. Connectors API](https://apis.io/apis/infolang-ai/infolang-ai-connectors-api/)
- [InfoLang Inc. Disclosures API](https://apis.io/apis/infolang-ai/infolang-ai-disclosures-api/)
- [InfoLang Inc. Health API](https://apis.io/apis/infolang-ai/infolang-ai-health-api/)
- [InfoLang Inc. Identity API](https://apis.io/apis/infolang-ai/infolang-ai-identity-api/)
- [InfoLang Inc. Ingest API](https://apis.io/apis/infolang-ai/infolang-ai-ingest-api/)
- [InfoLang Inc. Inquiries API](https://apis.io/apis/infolang-ai/infolang-ai-inquiries-api/)
- [InfoLang Inc. Kairos passthrough API](https://apis.io/apis/infolang-ai/infolang-ai-kairos-passthrough-api/)
- [InfoLang Inc. Keys API](https://apis.io/apis/infolang-ai/infolang-ai-keys-api/)
- [InfoLang Inc. Members API](https://apis.io/apis/infolang-ai/infolang-ai-members-api/)

## Tags

Correspondences

---

Profiled by [API Evangelist](https://apievangelist.com) and published on [APIs.io](https://apis.io/apis/infolang-ai/infolang-ai-correspondences-api/). The API's provider profile, Kin Score and agent-readiness rating are at https://apis.io/providers/infolang-ai/.