Inspect retrieval. Trace the answer.

Build account-owned collections, follow the matches that shaped an answer and keep source context visible before it reaches a model.

Retrieval transaction

Follow a query from match to cited answer.

Follow the selected passage into the cited answer. A nearby billing passage is left out because it does not answer the policy question.

Open API reference
Semantic query POST /api/v1/query

Can raw payment card data be sent to a gateway tool?

Returned passages top: 2 · includeReferences: true
01 / Evidence kept security/tool-boundaries

Before a tool call, payment card numbers must be redacted from the arguments and replaced with a tokenized reference.

This is the rule the answer cites: redact the card number and use a tokenized reference.

Related, but not usedbilling/refunds

Refund operations retain an invoice reference and the approved amount in the billing record.

This passage concerns billing records, not what a gateway tool may receive.

Inspect the illustrative ranking scores

Initial retrieval and reranking are different stages. These illustrative scores are not probabilities or a shared measure of improvement; the selected passage remains first in this example.

Scores by stage — illustrative only
PassageRetrievalReranking
security/tool-boundaries0.820.91
billing/refunds0.770.69

Knowledge capabilities

AIVAX / Provenance

Evidence stays useful when its place in the record remains intact.

An archival conservation room with records arranged in sequence across a long worktable

Ask for evidence, an answer, or both.

/api/v1/query

Search

Return the evidence when the application will make the final decision.

/api/v1/answer

Answer

Draft an answer while keeping the retrieved sources beside it.

AI Gateway

Ground

Reuse the same retrieval policy behind every compatible chat call.

Attach the collection to an AI Gateway.

See gateway inference