OpenAPI Example Runner

Store Positioning

Store title: OpenAPI Example Runner

Short description: Extract and run safe bounded examples from OpenAPI specs and report pass/fail results.

SEO title: OpenAPI Example Runner — API, schema, and developer QA

SEO description: Extract and run safe bounded examples from OpenAPI specs and report pass/fail results. Use it to catch contract drift, schema mistakes, unsafe endpoint assumptions, and developer-tool quality issues before release.

Categories: DEVELOPER_TOOLS

Keywords: openapi, example, runner, api testing, api/developer qa

Fixed-Inclusive PPE Pricing

This actor uses pay-per-event pricing. Event prices include Apify platform usage; users are not expected to pay a separate platform-usage pass-through charge for the configured pricing model.

• Tier: A1 — API/developer QA
• Primary event: schema-validated at $0.00650 base
• Default max charge: $10.00
• Store discounts: FREE/BRONZE base, SILVER discounted, GOLD deepest approved discount

Event set:

• actor-start: base $0.00500, GOLD $0.00400. Openapi Example Runner: charged when actor start is completed. The price includes Apify platform usage; no separate usage pass-through is intended.
• schema-validated: base $0.00650, GOLD $0.00520. Openapi Example Runner: charged when schema validated is completed. The price includes Apify platform usage; no separate usage pass-through is intended.
• contract-rule-checked: base $0.00390, GOLD $0.00312. Openapi Example Runner: charged when contract rule checked is completed. The price includes Apify platform usage; no separate usage pass-through is intended.
• report-generated: base $0.05000, GOLD $0.04000. Openapi Example Runner: charged when report generated is completed. The price includes Apify platform usage; no separate usage pass-through is intended.

Public Task Concepts

• Validate OpenAPI Example Runner before release
• Run a bounded OpenAPI Example Runner QA check
• Audit openapi issues across supplied public inputs
• Extract evidence-backed openapi rows for client QA
• Generate developer QA evidence for OpenAPI Example Runner

What It Does

Extract and run safe bounded examples from OpenAPI specs and report pass/fail results.

This local package is part of the Junipr Apify actors 171-200 premium build for ChatGPT review.

What It Does Not Do

• It does not call live Apify APIs.
• It does not publish, upload Store assets, create public tasks, or configure live PPE.
• It does not claim publish readiness.
• It does not make unbounded network calls in the supplied examples path.

Input Fields

Seed shape: openapiSpecJson or openapiSpecUrl, baseUrl, maxExamples, timeoutMs, skipUnsafeMethods

The tiny fixture is available at examples/input.tiny.json and mirrored at fixtures/input.tiny.json for the local runner.

Output Fields

• operationId
• method
• path
• exampleName
• requestUrl
• statusCode
• passed
• responseTimeMs
• schemaValid
• skippedReason
• error
• warnings
• recommendation

Public Task Examples

Run OpenAPI examples against sample responses

• Search intent: run openapi examples against sample responses
• Specific input: Capped input shaped for run openapi examples against sample responses.
• Expected output: Dataset rows with operationId, method, path, exampleName plus local KVS report evidence.
• Why run it: API teams, DevRel, platform teams, QA would run this to get a bounded local proof before any live Apify review or production use.

Skip unsafe OpenAPI operations in a fixture run

• Search intent: skip unsafe openapi operations in a fixture run
• Specific input: Capped input shaped for skip unsafe openapi operations in a fixture run.
• Expected output: Dataset rows with operationId, method, path, exampleName plus local KVS report evidence.
• Why run it: API teams, DevRel, platform teams, QA would run this to get a bounded local proof before any live Apify review or production use.

Validate example responses for GET endpoints

• Search intent: validate example responses for get endpoints
• Specific input: Capped input shaped for validate example responses for get endpoints.
• Expected output: Dataset rows with operationId, method, path, exampleName plus local KVS report evidence.
• Why run it: API teams, DevRel, platform teams, QA would run this to get a bounded local proof before any live Apify review or production use.

Create request rows from an OpenAPI specification

• Search intent: create request rows from an openapi specification
• Specific input: Capped input shaped for create request rows from an openapi specification.
• Expected output: Dataset rows with operationId, method, path, exampleName plus local KVS report evidence.
• Why run it: API teams, DevRel, platform teams, QA would run this to get a bounded local proof before any live Apify review or production use.

Review operation examples before API documentation release

• Search intent: review operation examples before api documentation release
• Specific input: Capped input shaped for review operation examples before api documentation release.
• Expected output: Dataset rows with operationId, method, path, exampleName plus local KVS report evidence.
• Why run it: API teams, DevRel, platform teams, QA would run this to get a bounded local proof before any live Apify review or production use.

Tests

• Actor-specific fixture tests live in test/openapi-example-runner.test.ts.
• Node-based local suites validate dataset schema conformance, output samples, local smoke runs, and PPE guard behavior.

FAQ

Is this live on Apify?

No. This is a local package for ChatGPT review only.

Is it publish-ready?

No. It needs later live tiny-run validation and console configuration before any publication decision.