# InfoLang Inc. Warrants API

**Canonical:** https://apis.io/apis/infolang-ai/infolang-ai-warrants-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. Warrants 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 Warrants. The published artifact set on APIs.io includes an OpenAPI specification.

WHY a memory stands, and what falls with it — `il-warrant`'s support/defeat algebra pointed at memory. An edge is an exact, stated REASON; withdrawing one is an append, never a delete, so the reason and its retraction both stay in the log forever. `GET …/memories/{id}/warrant` answers the traceability question in one call: what stands behind this memory, and which claims would change if this premise were discounted (ONE HOP — never the transitive closure). Recall can annotate every hit (`warrants: true`), and a memory nobody has argued about reads as `examined: false` rather than as `unsupported`. 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}/warrants` | State a reason |
| POST | `/v2/workspaces/{id}/warrants/{edge}/bottom` | Withdraw a reason (an append, never a delete) |
| GET | `/v2/workspaces/{id}/warrant-status` | What is accepted about one ref, and on what evidence |
| GET | `/v2/workspaces/{id}/warrant-impact` | What one hop of discounting this premise would reach |
| GET | `/v2/workspaces/{id}/warrants/{edge}` | One edge, everything the log holds about it |
| GET | `/v2/workspaces/{id}/memories/{memoryId}/warrant` | What stands behind this memory, and what leans on it |

## Machine-readable artifacts (1)

- **OpenAPI** — https://artifacts.apis.io/infolang-ai/openapi/infolang-ai-warrants-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. Correspondences API](https://apis.io/apis/infolang-ai/infolang-ai-correspondences-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/)

## Tags

Warrants

---

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