Document Structured Extraction
Try Document Structured Extraction on us. Starter credit covers your first requests, then one key reaches this route and every other model in the catalog.
neurometric/document-structured-extraction
| Publisher | Neurometric AIneurometric |
|---|---|
| AI IQ | No AI IQ profile matched yet. |
| Context | 49,152 tokens |
| Providers | |
| Credits routes | 1 provider route |
| Modes | chat US providers |
| Billing | Credits |
How to use Document Structured Extraction
Extracts caller-selected fields from invoices, contracts, forms, tickets, and other document text into typed JSON.
| Input | Put one JSON object in the user message with document containing the source text and output_schema mapping every requested field to its expected type, such as string, number, boolean, or string|null. Explicitly request every field you need. Missing nullable values are returned as null. |
|---|---|
| Output | Returns only one JSON object containing exactly the requested fields and types. Source text is copied exactly unless a number or boolean is requested. Requested fields that are absent are returned as null. |
Example input
{
"document": "INVOICE A-1042. Vendor: Acme Supply. Total due: USD 87.25.",
"output_schema": {
"invoice_number": "string",
"vendor": "string",
"total": "number",
"currency": "string"
}
}
Example output
{
"invoice_number": "A-1042",
"vendor": "Acme Supply",
"total": 87.25,
"currency": "USD"
}
Current route evidence
Live leaderboardRecent provider-route uptime spans 100.00% across 1 route and 1 provider. Price comes from the current Credits catalog. Speed and uptime come from routed probes rather than vendor claims.
Providers serving this model
Sorted by lowest combined prompt and completion price. Use
"provider": {"sort": "throughput"} in the request body
(or append :nitro to the model id) to route to the
fastest provider instead.
Trust boundary: TR router attestation verifies the TrustedRouter gateway only. Provider policy separately describes the upstream model host's retention, confidential compute, and E2EE posture. Company country is separate from inference location. Weight formats are source-backed declarations, not per-request proofs.
| Provider | Input | Cached input | Output | Weight format | Provider policy | Company / inference location | Measured speed |
|---|---|---|---|---|---|---|---|
| Neurometric AIneurometric | $0.01055/1M | Not published | $0.1055/1M | Unknown |
no verified privacy claim
Retention detailsNeurometric states that TrustedRouter requests run with upstream trace logging disabled: prompts and completions are not written to observability or object storage, and only aggregate request counts and token totals are retained. This is classified as no-store, not contractual ZDR or confidential compute. |
Operator country: US
Location detailsHeadquarters / registered office: Not verified. Inference: AWS us-west-2, provider-submitted hosting declaration; not a per-request receipt. Neurometric supplied AWS us-west-2 in its marketplace application. New models and exhaustive failover locations need separate confirmation. Region pinning through TR: Not supported by the current TrustedRouter integration. Reviewed 2026-09-27. |
TTFT: 2.36 s
Speed: insufficient data
Last sample:
|
Speed is the median (p50) from TR's recent measured requests for this exact model and provider, refreshed from the cached leaderboard. At least two timing samples are required; workload and network conditions affect results. Performance details
Endpoint JSON: https://api.trustedrouter.com/v1/models/neurometric/document-structured-extraction/endpoints
Compare Document Structured Extraction
All comparisons- MoonshotAI: Kimi K3 vs Document Structured Extraction29 combined provider routes
Questions
What model ID should I use for Document Structured Extraction?
Use neurometric/document-structured-extraction as the model field with the TrustedRouter OpenAI-compatible API. Credits routing and provider fallback happen behind that model ID.
Which providers serve Document Structured Extraction?
TrustedRouter currently lists Neurometric AI for Document Structured Extraction. Provider availability and routing eligibility can change as catalog and health data update.
How much does Document Structured Extraction cost through TrustedRouter?
The current lowest Credits input price is $0.01055/1M and the lowest Credits output price is $0.1055/1M. Prices are per one million tokens and come from the current route catalog.
How do I require zero data retention for Document Structured Extraction?
Set provider.min_privacy to zdr on the request. TrustedRouter considers only routes with a recorded zero-data-retention posture and fails closed if no eligible route remains.