More screenshots

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    Specseal: Agree the API contract before you build it

    1

    Validated schemas, one error shape, status-code rules, pagination, idempotency keys, scopes and rate limits in one OpenAPI file or typed contract, with contract tests and a breaking-change checklist.

    $15

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Specseal: Agree the API contract before you build it

    Specseal: Agree the API contract before you build it

    Example session with this skill installed

    Specseal, review our job board API before the mobile app launches. Routes are in src/routes (Express + Zod). Tell me what to fix first.

    • Read your context and instructions
    • Compiled the specseal

    Reviewed 6 endpoints in src/routes (example project). Consumers: web app, mobile app (cannot update instantly), nightly cron.

    EndpointIssueSeverityFix
    GET /jobPostsReturns every row, no pagination; path not kebab-caseHighCursor pagination, default 20, max 100; rename to /job-posts
    GET /job-posts/{id}200 with an error body when missingHigh404 with code JOB_NOT_FOUND
    POST /applicationsNo idempotency; a retry creates a duplicateHighAccept Idempotency-Key, store key, caller and response hash with a TTL
    PATCH /users/{id}Any signed-in user can edit any idHighOwnership check; 404 when not visible to the caller
    POST /auth/loginNo rate limitMediumPer-caller limit, 429 with Retry-After
    GET /teams/{id}/members/{mid}/rolesNested two levelsLowMove to /members/{mid}/roles

    4 high, 1 medium, 1 low. Fix the error shape and validation first:

    { "error": { "code": "JOB_NOT_FOUND", "message": "Job not found", "details": [], "requestId": "req_7f3a" } }
    

    Breaking for the mobile app: the /jobPosts rename and the new page-size default. Ship both under /v1 with a Sunset header on the old route, or agree a migration window with the mobile team.

    Next steps

    • Add the central error handler and the shared error schema.
    • Write openapi.yaml and contract tests for the 4 high items.
    • Run the breaking-change checklist against the deployed contract before ship.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Every route returns its own error format, a renamed field crashes the mobile app that cannot update, and a retried POST creates the order twice. The cause is that nobody agreed what the API promises. Specseal writes that contract first, so clients, tests and docs come from one source.

    What it does

    • Use-case first design derives endpoints from each consumer's actor, action, data in and data out, not from the tables.
    • Validated schemas check params, query, body and headers at the boundary with the schema library your stack already has (Zod, Pydantic, JSON Schema).
    • One success and one error shape with stable machine codes, field-level validation details and a request id.
    • Status-code rules, including "never 200 with an error body".
    • Lists, retries and scopes: every list paginated with a max page size, an Idempotency-Key on retry-sensitive POSTs, scopes and ownership checks on every path id.
    • Rate limits and versioning written into the contract, with 429 plus Retry-After and a deprecation path for breaking changes.

    How it works

    1. Consumers and naming: one line per use case, then plural kebab-case paths, one field case and nesting of at most one level.
    2. Schemas and rules: request, response and error schemas per endpoint, with the rules above applied.
    3. Contract as source: an OpenAPI 3.1 file or a typed schema module that generates OpenAPI, linted in CI.
    4. Contract tests: valid request, each documented error, missing auth, wrong owner and idempotent replay.
    5. Breaking-change checklist: the contract is diffed against the deployed version before ship.

    Frameworks & tools

    OpenAPI 3.1 or a typed schema module, using Zod, Pydantic or JSON Schema. Variants cover internal apps, public APIs, API reviews and webhook providers.

    Why this beats prompting it yourself

    A plain prompt designs endpoints one at a time and lets each one invent its own rules. Specseal applies one rule set across the whole API, traces every endpoint to a use case, and ends with contract tests and a breaking-change diff.

    Use cases

    • New backends designed before handlers exist.
    • Payload disputes between frontend and backend.
    • Partner or mobile APIs whose clients cannot update instantly.
    • Live endpoint changes checked for breakage.

    Known limitations

    Does not design database tables or migrations, and does not cover credit or payment idempotency inside a ledger. For a server-rendered page with no external client, a typed server function may be enough.

    Does not design database tables or migrations, and does not cover credit or payment idempotency inside a ledger. For a server-rendered page with no external client, a typed server function may be enough.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 29 days ago

    Requires

    OpenAPI 3.1
    Zod
    Pydantic
    JSON Schema

    Permissions

    Write Files
    Network Access
    Listed29 days ago

    What's inside

    Frequently Asked Questions

    Access to the repo or a description of who calls the API. It reads the README, package manifest and config files to find the stack, and asks once for anything still missing.

    No. Table design and migrations are out of scope, as is credit or payment idempotency inside a ledger. It covers the contract that sits in front of them.

    A plain prompt writes a spec. Specseal starts from consumers and use cases, applies one error shape and the same status, pagination, idempotency, scope and rate-limit rules to every endpoint, then adds contract tests and a breaking-change check before ship.

    The zip contains SKILL.md (the instructions your agent follows) and LICENSE.md. Nothing else is installed. It works with the schema library your stack already uses.

    New in APIs & Backend