POST

Issuer Launchpad

Query finalized evidence

/api/v2/launchpad/offerings/{offering_id}/agent/query
AUTHENTICATIONNone · publicService ownerlaunchpad-serviceContract sourceOpenAPISTATUSProduction listed

Purpose and usage

What this endpoint does

Ask a bounded question over finalized disclosed claims and receive citation-bearing answers tied to release and manifest evidence.

When to use it

Use for a bounded natural-language question whose answer must be grounded only in finalized public claims for this offering.

OUTCOME · Create or advance

What changes

Read-only evidence query. It cannot expose private diligence, infer undisclosed facts, recommend an investment, or initiate a transaction.

WHY IT MATTERS

  • Gives people and agents a contract-backed way to advance query finalized evidence.
  • Connects private issuer preparation to public, citation-bearing disclosure without exposing draft evidence or collapsing review, signature, finality, and availability into one state.

ISOLATION + AUTHORITY

Workspace, issuer, offering, security-class draft, Data Vault object version, requirement pack, diligence case, evidence view, reviewer decision, auditor attestation, release, signer, validator finality, replication, public index, and investor eligibility remain distinct. Launchpad cannot issue, mint, custody, sell, trade, match, settle, or authorize an investment, and its public routes expose only finalized disclosure evidence.

BEFORE YOU CALL

  • No bearer credential is required; apply bounded filters and canonical public identifiers where the contract provides them.
  • Supply the required offering_id (path), question (body) exactly as defined by the live contract.
  • Resolve the authenticated workspace and derived issuer, reviewer, auditor, signer, or publisher authority for this stage; use exact Data Vault versions and distinguish private preparation from finalized public disclosure.

WHAT TO DO NEXT

  • Re-read query finalized evidence using the canonical identifier returned by this operation.
  • Reconcile an ambiguous response with the same idempotency key before attempting another mutation.
  • Follow returned canonical identifiers and commitments into the next explicit Launchpad stage, re-attesting protected evidence and re-reading release finality before public reliance.

AGENT GUIDANCE

  • Use query finalized evidence only for the purpose and lifecycle stage described by this operation; do not treat it as authority for an adjacent action.
  • Supply the required offering_id (path), question (body) exactly as defined by the live contract.
  • Keep draft creation, evidence linking, evidence-view pinning, review, attestation, release assembly, freeze, signature, submission, validator finality, replicated availability, indexing, and supersession as separate lifecycle facts.
  • After a timeout or conflict, read authoritative state before deciding whether an equivalent retry is safe.
Contract reference

Use the deployed OpenAPI for exact parameters, schemas and security requirements. The tables below provide integration guidance.

Open this operation in OpenAPI

Request and response

Make the request

Examples illustrate integration intent; the referenced OpenAPI operation and component schemas define the executable shape.

PARAMETERS

Headers, path, query, and body

NAMELOCATIONPRESENCETYPE / RULES / PURPOSE
offering_idpathRequired

identifierStable offering id selecting the exact resource addressed by this route.EXAMPLEoffering-id-01

X-Request-IDheaderOptional

stringOptional caller correlation identifier. The gateway emits the effective value on the response.

as_ofbodyOptional

RFC 3339 timestampOptional historical cutoff for append-only disclosure reconstruction.EXAMPLE2026-09-01T12:00:00Z

questionbodyRequired

string · 1–500Bounded natural-language question answered only from finalized disclosed claims.EXAMPLEWhat revenue did the issuer disclose?

REQUEST

JSON body example

{
  "as_of": "2026-09-01T12:00:00Z",
  "question": "What revenue did the issuer disclose?"
}

RESPONSES

Status and payload examples

201Mutation accepted and canonical state returned.Mutation completed · JSON RESPONSE+
{}
INTEGRATION DECISION
CALLER ACTION
Accept the returned representation or receipt, then re-read query finalized evidence using the canonical identifier returned by this operation.
RETRY SAFETY
Do not repeat a successful mutation merely to confirm it. This mutation has no documented idempotent replay contract. Reconcile state before considering another attempt.
STATE RECONCILIATION
Persist returned identifiers, versions, commitments, and receipts. Refresh the offering revision, evidence commitments, review and disclosure status, readiness milestone, issuer authority, and publication or finality receipt.
422Path, query, or body validation failed.Request must change · JSON RESPONSE+
{
  "code": "invalid_credentials",
  "message": "the supplied Hybrid credential is invalid"
}
INTEGRATION DECISIONinvalid_credentials
CALLER ACTION
Rebuild the request from the live OpenAPI operation and correct the rejected method, media type, header, parameter, or body field.
RETRY SAFETY
Do not retry the same invalid request. This mutation has no documented idempotent replay contract. Reconcile state before considering another attempt.
STATE RECONCILIATION
Compare the submitted values with the documented constraints before another call. Refresh the offering revision, evidence commitments, review and disclosure status, readiness milestone, issuer authority, and publication or finality receipt.
ESCALATE WHEN
Escalate when issuer authority, diligence evidence, disclosures, approvals, publication, or chain finality cannot be matched to one immutable revision.
503The authoritative service or read model is unavailable.Dependency unavailable or outcome uncertain · JSON RESPONSE+
{
  "code": "invalid_credentials",
  "message": "the supplied Hybrid credential is invalid"
}
INTEGRATION DECISIONinvalid_credentials
CALLER ACTION
Preserve the exact request and treat the outcome as uncertain until authoritative state proves whether it committed.
RETRY SAFETY
Reconcile before retrying. This mutation has no documented idempotent replay contract. Reconcile state before considering another attempt. Use bounded backoff with jitter.
STATE RECONCILIATION
Refresh the offering revision, evidence commitments, review and disclosure status, readiness milestone, issuer authority, and publication or finality receipt.
ESCALATE WHEN
Escalate when issuer authority, diligence evidence, disclosures, approvals, publication, or chain finality cannot be matched to one immutable revision.

OPERATIONAL NOTES

Security and lifecycle guarantees

  • Ask a bounded question over finalized disclosed claims and receive citation-bearing answers tied to release and manifest evidence.
  • The Rust gateway validates the public contract and routes only to the authoritative owner; clients never address internal services directly.
  • The tables and examples are derived from the current gateway source OpenAPI. Re-fetch the deployed OpenAPI before execution; deployment status is shown separately on this page.
  • Only parameters present in the OpenAPI operation are accepted; undocumented query keys fail closed with HTTP 422.
Reference version and availability details

This route is implemented in canonical gateway source and appears in the production OpenAPI snapshot observed 2026-10-02T23:27:55.510Z. Authentication, tenant, feature, venue, and market policy still apply.

Verify the exact production OpenAPI operation Return to the V2 directory