TESSA Marketing & Technology

TESSA Marketing & Technology .well Known API

The .well Known API from TESSA Marketing & Technology — 3 operation(s) for .well known.

Documentation GitHub OpenAPI

Operations 3

GET /.well-known/agent-card.json Well Known Agent Card #

GET /.well-known/did.json Well Known Did Document #

GET /.well-known/mcp/server.json Mcp Server Manifest #

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/tessa-tech:tessa-tech-well-known-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.

GitHub Google LinkedIn

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

OpenAPI Specification

openapi: 3.2.0
info:
  title: TESSA Agent Directory .well Known API
  version: 0.1.0
  description: 'TESSA Marketing & Technology''s FastAPI service behind aiagent.tessa.tech: the A2A agent card and JSON-RPC endpoint, per-service and per-tenant agent cards, the professional-services directory (firm cards, profiles, introduction requests, claim/verify/removal/takedown flows), the TESSA Professional Services A2A extension, service-type taxonomies, an admin/vector surface, and the mount point of the MCP server (/mcp, Streamable HTTP).'
  contact:
    name: TESSA Marketing & Technology
    url: https://tessa.tech
    email: sales@tessa.tech
  x-apievangelist-provenance:
    harvested: '2026-09-19'
    method: searched
    source: https://aiagent.tessa.tech/openapi.json
    original: openapi/_original/tessa-tech-openapi.json
    original_sha256: 3349c7e2613aca4fb5736b570f082a2d509e1147b8a82183b71dafff0722f6da
    changes:
    - servers[] added (the harvested spec declares none); hosts taken from the provider's own root document at https://aiagent.tessa.tech/ and verified by an identical-byte spec at complianceregistry.net/openapi.json and marketingregistry.org/openapi.json
    - info.description and info.contact added; contact values from the agent card (_meta.tessa.contact) and server.json (support_email)
    ownership: Served on tessa.tech's own subdomain; info.title names TESSA; the agent card at the same host names TESSA Marketing & Technology as provider with url https://tessa.tech; the root document names the app 'TESSA MCP Server + Agent Directory'.
servers:
- url: https://aiagent.tessa.tech
  description: TESSA's own agent host — agent card, A2A JSON-RPC, MCP (/mcp/), service cards (/s), OpenAPI. Registry-scoped routes return 421 here.
- url: https://complianceregistry.net
  description: TESSA-operated Compliance Registry (same application, same spec bytes). Registry routes (/registry.json, /taxonomy, /extensions, /{slug}) resolve here.
- url: https://marketingregistry.org
  description: TESSA-operated Local Business / Marketing Registry (same application, same spec bytes).
tags:
- name: .well Known
paths:
  /.well-known/agent-card.json:
    get:
      summary: Well Known Agent Card
      operationId: well_known_agent_card__well_known_agent_card_json_get
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema: {}
      tags:
      - .well Known
  /.well-known/did.json:
    get:
      summary: Well Known Did Document
      description: Backs did:web:tessa.tech — tessa.tech/.well-known/did.json 301s here.
      operationId: well_known_did_document__well_known_did_json_get
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema: {}
      tags:
      - .well Known
  /.well-known/mcp/server.json:
    get:
      summary: Mcp Server Manifest
      description: 'The MCP registry manifest for whichever host was asked.


        aiagent.tessa.tech serves server.json; each registry domain serves its own

        server-.json (the files had been in the repo since Phase 1b, but this

        route only ever answered on the ''mcp'' surface, so both registries 404''d).'
      operationId: mcp_server_manifest__well_known_mcp_server_json_get
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema: {}
      tags:
      - .well Known