# InfoLang Inc. Inquiries API

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

WHAT IS STILL BEING ASKED — `il-inquiry` pointed at the corpus. Every knowledge system files the answer and throws the question away, and is then structurally unable to say what is OUTSTANDING, who narrowed it into what, or that the question being answered today is not the one originally asked. For an intelligence operation that is the PIR/RFI loop verbatim. Refining a question does not answer it (IR2), splitting one supersedes it rather than answering it (IR3), an answer must NAME its evidence (IR4), and an agenda row is an equivalence CLASS rather than a question (IR6). Recall can annotate every subjected hit (`inquiries: true`) with the outstanding questions on its key, and filter to them (`only_outstanding`) — and a memory NEVER answers a question by arriving on its subject. All three lanes, gated on `coord:read` / `coord:write`; `501` where the upstream kernel verbs are not compiled in.

## Operations (9)

| Method | Path | Summary |
|---|---|---|
| POST | `/v2/workspaces/{id}/inquiries` | Open a question |
| POST | `/v2/workspaces/{id}/inquiries/{inquiry}/narrow` | Refine a question — WITHOUT answering it |
| POST | `/v2/workspaces/{id}/inquiries/{inquiry}/split` | Decompose a question into children |
| POST | `/v2/workspaces/{id}/inquiries/{inquiry}/answer` | Answer a question by naming the assertion that answers it |
| POST | `/v2/workspaces/{id}/inquiries/{inquiry}/abandon` | Give up on a question, with a reason |
| POST | `/v2/workspaces/{id}/inquiries/{inquiry}/reopen` | Reverse one abandonment |
| POST | `/v2/workspaces/{id}/inquiries/same-as` | Declare two questions to be one agenda row |
| GET | `/v2/workspaces/{id}/agenda` | What is still outstanding |
| GET | `/v2/workspaces/{id}/inquiries/{inquiry}` | One question's whole history |

## Machine-readable artifacts (1)

- **OpenAPI** — https://artifacts.apis.io/infolang-ai/openapi/infolang-ai-inquiries-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. 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

Inquiries

---

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