Use when
- An agent needs a clearly synthetic fixture for a supported schema.
- Tests need deterministic data without copying production records.
fixtures · beta · free
Generate repeatable identity, network, or HTTP-event fixtures without inventing a real person, inbox, domain, or routable address. The same kind and seed produce the same fixture.
{
"input": {
"kind": "network",
"seed": "crawl-test-42"
},
"output": {
"kind": "network",
"deterministic_id": "sha256:eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee",
"fixture": {
"domain": "a1b2c3d4e5f6.example.invalid",
"ipv4": "192.0.2.42",
"url": "https://a1b2c3d4e5f6.example.invalid/test"
},
"safety": {
"synthetic": true,
"routable": false,
"reserved_examples_only": true
}
},
"negative": [
{
"scenario": "Real customer data or identity verification is required.",
"expected_error": "INVALID_INPUT",
"charged": false
}
]
}| Code | Retry | Charged | Recovery |
|---|---|---|---|
| INVALID_INPUT | false | false | Correct the request to match input_schema. |
| TOOL_PAUSED | true | false | Wait for the operator to resume the tool. |
| RATE_LIMITED | true | false | Retry after the response Retry-After interval. |
| DEPENDENCY_UNAVAILABLE | true | false | Retry with the same idempotency identity. |
The HTTP, OpenAPI, MCP, llms.txt, and ARD descriptions are generated from this same registry record.