Find files, editable templates and browser test targets by what you need to make or test. Explore complete business kits for connected records, templates and expected results.
Page 140 of 221; 24 results per page.
JSON openai-compatible prompt 04 for the planning phase of a short documentary; it asks for assumptions, reversible actions, and explicit acceptance checks. Stable P8 artifact p8-prompt-094.
JSON openai-compatible prompt 03 for the planning phase of a software tutorial; it asks for assumptions, reversible actions, and explicit acceptance checks. Stable P8 artifact p8-prompt-093.
JSON openai-compatible prompt 06 for the planning phase of a studio interview; it asks for assumptions, reversible actions, and explicit acceptance checks. Stable P8 artifact p8-prompt-096.
JSON openai-compatible prompt 13 for the planning phase of a travel field note; it asks for assumptions, reversible actions, and explicit acceptance checks. Stable P8 artifact p8-prompt-103.
A small but complete OpenAPI 3.1 description (two paths, three schemas) in JSON, for testing API tooling, mock servers, client codegen, and docs generators.
The same OpenAPI 3.1 description in YAML: the format most API definitions ship in. Paired with the JSON twin for testing YAML↔JSON conversion and spec parsers.
Minimal OpenAPI 3.1 document with a webhooks section, for testing webhook-aware spec parsers.
Callback payload matching the Wave F webhook OpenAPI SAMPLE.
OpenAPI document with empty paths but populated components. Tests partial spec loaders.
Sample POST /pets request body matching the pet-store OpenAPI spec.
Sample 404 problem response for OpenAPI error-handling tests.
Sample paginated pet list response for mock-server and contract tests.
The compatible member of a complete OpenAPI 3.1 ticket endpoint contract. Backward compatible: an optional priority response property is added and existing operations stay unchanged.
The baseline member of a complete OpenAPI 3.1 ticket endpoint contract. Reference API: string ticket IDs and required id/summary response properties.
The breaking member of a complete OpenAPI 3.1 ticket endpoint contract. Breaking relative to baseline: ticket id becomes integer and status becomes a required response property.
SAMPLE OpenID Connect discovery document for OIDC client and metadata parsers.
A complete OpenMetrics document (the _total and _created series a counter really has, UNIT metadata, an info metric carrying build metadata and a stateset with exactly one active state) terminated by the mandatory # EOF. This is what the exposition format became once it was standardised.
Histogram buckets carrying exemplars whose trace_id and span_id resolve against the OTLP trace fixtures in this category: the exact-to-example link that turns a latency spike on a graph into a specific request. Five exemplars, each with its own observed value and timestamp.
A document that parses perfectly as Prometheus text and is invalid as OpenMetrics, because the mandatory # EOF terminator is missing. That marker is the format's only defence against a truncated response being accepted as complete, which is the exact failure this file reproduces.
ASCII-armored SAMPLE-shaped PGP public key placeholder for armor detectors (not a cryptographically valid key).
Six tail-sampling policies including an inverted regex match that drops health checks and a composite policy with its own rate limit and ordered sub-policies. Policies are OR-ed and one match keeps the entire trace, which is the semantic most people get backwards.
A Collector configuration wiring traces, metrics and logs through separate pipelines, with named component instances, a filelog receiver that parses the CRI log fixture, OTTL statements performing the semantic-convention migration from the paired trace fixtures, and a redaction processor.
An OpenVEX document covering all four status values, with the justification and impact statement OpenVEX requires alongside not_affected and the action statement it requires alongside affected. Advisory identifiers use the invented NOVUS-SAMPLE namespace with SAMPLE-CVE aliases; no identifier here refers to a published CVE, GHSA or OSV record, and no package named exists.
We use Google Analytics and show ads via Adsterra. Non-essential cookies and ad scripts run only after you allow the matching categories. See our cookie policy.
