GOVERNATLAS / PRODUCT DOSSIER

Respan

Respan describes model routing, tracing, evaluation and monitoring; the previous Keywords AI domain redirects to this current identity.

Explore the product ↗Add to comparison ↗

01 / CONTEXT & SCOPE

Understand the proposition.
Define the boundary.

The decision to make

Map routing and evaluation as separate decisions even when they share a platform. A fallback can change the provider, model, region or output behavior while a single endpoint stays the same. Confirm that the trace identifies the effective route and that a sampled evaluation does not get reported as complete production coverage.

What this record does not establish

The prior Keywords AI domain redirects to Respan; one current identity is recorded. Advertised uptime, model count, savings, certification and regulatory compliance are not adopted as independent findings.

1 current source · 1 published assertion
Source coverage is a research boundary, not a quality score.

02 / YOUR EVALUATION

Turn interest into a useful trial.

Open the evaluation playbook ↗

A test worth running

Use fictional requests with an authorized simulated provider failure. Compare the original route and fallback under one rubric; inspect cache hits, retry behavior and the final provider on the trace. Include one request outside the evaluation sample and keep it outside the reviewed denominator.

GovernAtlas editorial proposal. We have not performed this test.

Evidence to bring back

A fallback/cache trace with the effective provider and configuration.
A sampling manifest linking evaluated cases to included and excluded traffic.

03 / DOCUMENTED EVIDENCE

Read the claim. Inspect the basis.

Each statement retains its classification and preserved source. A vendor assertion is not an independent test result.

vendor asserted

Respan describes model routing, tracing, evaluation and monitoring; the previous Keywords AI domain redirects to this current identity. Scope: primary documentation only; no independent product test, evaluator accuracy or compliance determination.

Source, dates & preserved provenance

Respan — primary scope and current identity ↗

Authority: vendor owned
Observed 2026-10-16 · Reviewed 2026-10-16 · current until 2026-11-15

Artifact SHA-256: c859f709c115ba8df4ba2bb38ed3b5eaa5f1b62c77d5a2f4ff2ca523d7dd9f78

The hash identifies the preserved capture. The live source may have changed.

Source register

Respan — primary scope and current identity ↗vendor owned · captured 2026-10-16

Brand asset provenance

Organization identity asset from its official website; inclusion does not imply endorsement.

Official website ↗ · Original asset ↗

04 / BEFORE YOU COMMIT

Better questions.
A clearer decision.

Resolve these with the provider and your own evaluation team.

Can you provide a fallback/cache trace with the effective provider and configuration for the selected configuration?

Can you provide a sampling manifest linking evaluated cases to included and excluded traffic for the selected configuration?

Which exact version, entitlements, data paths and responsible roles apply?

Regulatory applicability requires a separate, current determination. Inclusion is not certification.

KEEP THE RECORD USEFUL

A dossier should stand up to scrutiny.

Have a source that changes this picture? Submit it for editorial review.

Raise an evidence issue ↗