stipple-sh Meta API

Health, discovery, feedback, and cache-check endpoints.

Operations 2

POST /v1/feedback Submit Tool Feedback #
POST /v1/contact Submit Contact #

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API
curl "https://apis.io/api/v1/apis/stipple-sh:stipple-sh-meta-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

stipple-sh-meta-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: Stipple Sh Meta API
  version: 0.6.0
  contact:
    name: Stipple
    url: https://www.stipple.sh/contact
  license:
    name: Security & terms
    url: https://www.stipple.sh/security
  description: 'Operations tagged Meta across 2 of this provider''s published API definitions: www.stipple.sh-openapi.json, stipple-sh-openapi.json. Each path carries the servers of the definition it was published in.'
servers:
- url: https://www.stipple.sh
  description: Production
tags:
- name: Meta
  description: Health, discovery, feedback, and cache-check endpoints.
paths:
  /v1/feedback:
    post:
      tags:
      - Meta
      summary: Submit Tool Feedback
      description: 'Thumbs up/down for a stateless tool''s result (`tender_match`). Records a short,

        non-sensitive label. The rated text is stored ONLY

        plus the rated text when the caller sends it; retention and use are disclosed in the privacy

        policy. Best-effort: a write failure never fails the response.'
      operationId: submit_tool_feedback_v1_feedback_post
      requestBody:
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/ToolFeedbackBody'
        required: true
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema:
                additionalProperties: true
                type: object
                title: Response Submit Tool Feedback V1 Feedback Post
        '422':
          description: Validation Error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/HTTPValidationError'
    servers:
    - url: https://www.stipple.sh
      description: Production
  /v1/contact:
    post:
      tags:
      - Meta
      summary: Submit Contact
      description: 'Receive a contact-form message, from the /contact form or the site chat widget.


        Two sinks, and both matter. The message is written as ONE structured stdout line

        (jsonPayload.event="contact_message") that Cloud Run lands in Cloud Logging - the durable,

        queryable record - AND emailed to CONTACT_NOTIFY_TO, which is the part a person actually

        sees. The log alone was the original design and it failed in the obvious way: nobody

        queries a log, so real enquiries sat unread.


        Bot submissions (honeypot or impossibly-fast) are silently dropped before both sinks, on

        top of the rate limit.'
      operationId: submit_contact_v1_contact_post
      requestBody:
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/ContactBody'
        required: true
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema:
                additionalProperties: true
                type: object
                title: Response Submit Contact V1 Contact Post
        '422':
          description: Validation Error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/HTTPValidationError'
    servers:
    - url: https://www.stipple.sh
      description: Production
components:
  schemas:
    HTTPValidationError:
      properties:
        detail:
          items:
            $ref: '#/components/schemas/ValidationError'
          type: array
          title: Detail
      type: object
      title: HTTPValidationError
    ValidationError:
      properties:
        loc:
          items:
            anyOf:
            - type: string
            - type: integer
          type: array
          title: Location
        msg:
          type: string
          title: Message
        type:
          type: string
          title: Error Type
        input:
          title: Input
        ctx:
          type: object
          title: Context
      type: object
      required:
      - loc
      - msg
      - type
      title: ValidationError
    ToolFeedbackBody:
      properties:
        tool:
          type: string
          const: tender_match
          title: Tool
        verdict:
          type: string
          enum:
          - up
          - down
          title: Verdict
        ref:
          anyOf:
          - type: string
          - type: 'null'
          title: Ref
        note:
          anyOf:
          - type: string
          - type: 'null'
          title: Note
        sample:
          anyOf:
          - type: string
          - type: 'null'
          title: Sample
      type: object
      required:
      - tool
      - verdict
      title: ToolFeedbackBody
    ContactBody:
      properties:
        name:
          type: string
          title: Name
        email:
          type: string
          title: Email
        company:
          anyOf:
          - type: string
          - type: 'null'
          title: Company
        topic:
          anyOf:
          - type: string
          - type: 'null'
          title: Topic
        message:
          type: string
          title: Message
        website:
          anyOf:
          - type: string
          - type: 'null'
          title: Website
        elapsed_ms:
          anyOf:
          - type: integer
          - type: 'null'
          title: Elapsed Ms
      type: object
      required:
      - name
      - email
      - message
      title: ContactBody
x-refined-from:
- www.stipple.sh-openapi.json
- stipple-sh-openapi.json