Bridge Town getting started API

Bridge Town getting started API as documented publicly: 4 operations. Contract generated from the documentation by API Evangelist (2026-11-03); not the provider's own document.

Operations 4

GET /health Health endpoint GET /health (HTTP, unauthenticated) #
POST /health POST /health #
GET /mcp Connecting Claude.ai #
POST /mcp Bridge Town MCP endpoint (Streamable HTTP) #

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/bridgetown-builders:getting-started-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

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

bridgetown-builders-getting-started-openapi-generated.yml Raw ↑
openapi: 3.1.0
info:
  title: Bridge Town getting started API
  version: '2026-11-03'
  description: 'GENERATED FROM DOCUMENTATION by API Evangelist on 2026-11-03: 4 operation(s) read from 2 public documentation page(s) (each operation
    names its page in x-source). This is not the provider''s published contract; Bridge Town has published no machine-readable contract that the
    pipeline could find. Engine: local.'
  x-evidence-tiers:
    code-example: 5
    documentation: 28
    pages-with-code: 6
    pages-read: 13
  x-generated-from: documentation
  x-provenance: generated
  x-authored-by: API Evangelist
  x-generated: '2026-11-03'
  x-generator: generate-contract-from-docs.py
  x-engine: local
  x-sources:
  - https://www.bridgetown.builders/docs/getting-started/connect-claude-ai
  - https://www.bridgetown.builders/docs/getting-started/connect-mcp-client
  x-docs-section: getting-started
servers:
- url: https://api.bridgetown.builders
paths:
  /health:
    get:
      operationId: get_health
      tags:
      - Health
      summary: Health endpoint GET /health (HTTP, unauthenticated)
      description: The HTTP /health endpoint is unauthenticated and confirms the server is reachable.
      x-source: https://www.bridgetown.builders/docs/getting-started/connect-mcp-client
      responses:
        '200':
          description: Success (status as documented)
      x-evidence:
        kind: documentation
    post:
      operationId: post_health
      tags:
      - Health
      summary: POST /health
      x-source: https://www.bridgetown.builders/docs/getting-started/connect-mcp-client
      responses:
        '201':
          description: Success (status as documented)
      x-evidence:
        kind: code-example
        language: curl
        snippet: "curl : \n Terminal window curl -fsS https://api.bridgetown.builders/health \n The HTTP /health endpoint is unauthenticated and\
          \ confirms the server is\nreachable. To check authentication, hit the MCP endpoint with your token: \n Terminal window curl -fsS -X\
          \ POST https://api.bridgetown.builders/mcp \\ -H \" Authorization: Bearer btk_YOUR_TOKEN \" \\ -H \" Content-Type: application/json\
          \ \" \\ -H \" Accept: appli"
  /mcp:
    get:
      operationId: get_mcp
      tags:
      - Mcp
      summary: Connecting Claude.ai
      description: Used by Claude.ai for the SSE channel handshake when connecting via OAuth. The page only mentions the endpoint URL and its
        purpose, without detailing any query or body parameters or response schema.
      x-source: https://www.bridgetown.builders/docs/getting-started/connect-claude-ai
      responses:
        '200':
          description: Success (status as documented)
      x-evidence:
        kind: documentation
    post:
      operationId: post_mcp
      tags:
      - Mcp
      summary: Bridge Town MCP endpoint (Streamable HTTP)
      description: 'POST to the MCP endpoint with an Authorization: Bearer token and JSON-RPC payload to invoke Bridge Town tools.'
      x-source: https://www.bridgetown.builders/docs/getting-started/connect-mcp-client
      requestBody:
        required: true
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/PostMcpRequest'
      responses:
        '201':
          description: Success (status as documented)
      x-evidence:
        kind: documentation
security:
- bearer: []
components:
  schemas:
    PostMcpRequest:
      type: object
      properties:
        jsonrpc:
          type: string
          description: JSON-RPC version, e.g., "2.0"
        id:
          type: integer
          description: Request identifier
        method:
          type: string
          description: MCP method to invoke, e.g., "tools/list"
      required:
      - jsonrpc
      - id
      - method
  securitySchemes:
    bearer:
      type: http
      scheme: bearer
tags:
- name: Health
- name: Mcp