Bithart / Agent interface

Built for people.
Connected to agents.

Let your agent understand what we build and prepare a relevant introduction. You decide what gets shared. Our team takes the conversation from there.

Public discovery available · Submission activation pending

Arrange integration access Prefer to talk directly?

01 / Discover

Understand the fit.

Read our services, delivery approach and boundaries through a public, machine-readable interface.

02 / Get permission

Keep the person in control.

Show them the brief, the recipient and our privacy notice. Ask for permission for this specific introduction before sending.

03 / Introduce

A useful brief. A human next step.

An approved agent submits the brief and receives a delivery-service acknowledgement. Bithart reviews it before any next step.

For integration teams

A small, explicit interface.

HTTPS and structured JSON, documented with OpenAPI. This is a scoped project-introduction API, not an open-ended autonomous agent or an implementation of A2A JSON-RPC or MCP.

Live capabilities Services, boundaries and current intake status.
OpenAPI specification Request schema, authentication and response codes.
Discovery JSON Bithart’s custom discovery document.
LLM-readable overview A short index for agent research.

POST/api/agent/briefs

Server-side requests require an approved Bearer credential and an Idempotency-Key.

{
  "brief": {
    "company": "Example company",
    "email": "person@example.com",
    "problem": "We want to connect our CRM and internal knowledge so agents can prepare work for our team's approval."
  },
  "consent": {
    "granted": true,
    "purpose": "project_enquiry",
    "confirmedAt": "2026-09-30T12:00:00Z"
  }
}

Illustrative data only. Replace the example permission time with the actual time the person authorised the introduction. Keep credentials in your server’s secret store, never in browser code.

Clear boundaries, from the first request.

Permission is specific.

A public email address is not permission. The submitting client attests that the person approved the brief. This API does not independently verify their identity or consent. No prospect lists or unsolicited outreach.

Acceptance is not a promise.

A 202 response means the delivery service accepted the brief. It does not prove inbox delivery or human review, and never creates a booking, quote or contract.

Retries should not create more work.

Reuse the same body and request key after an uncertain result, within 24 hours. Honour Retry-After. If unsure after that window, contact us instead of sending again.

Discovery stays separate from action.

Reading our capabilities needs no key. Submission is limited to approved server-side clients. No attachments, callback URLs, arbitrary recipients, payments or access to other systems. Read the privacy notice.