TESSA Marketing & Technology

TESSA Marketing & Technology Request Introduction API

The Request Introduction API from TESSA Marketing & Technology — 1 operation(s) for request introduction.

Documentation GitHub OpenAPI

Operations 1

POST /{slug}/request-introduction Firm Request Introduction #

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-request-introduction-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 Request Introduction 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: Request Introduction
paths:
  /{slug}/request-introduction:
    post:
      summary: Firm Request Introduction
      description: 'Direct HTTP POST endpoint for the request-introduction skill.


        Body: { prospect_email, prospect_name?, prospect_org?, project_brief?, requested_window? }

        Returns: { status, tracking_id, target, delivery, message }'
      operationId: firm_request_introduction__slug__request_introduction_post
      parameters:
      - name: slug
        in: path
        required: true
        schema:
          type: string
          title: Slug
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema: {}
        '422':
          description: Validation Error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/HTTPValidationError'
      tags:
      - Request Introduction
components:
  schemas:
    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
    HTTPValidationError:
      properties:
        detail:
          items:
            $ref: '#/components/schemas/ValidationError'
          type: array
          title: Detail
      type: object
      title: HTTPValidationError