bettan Developers
Back to Bettan

Build on Bettan

Anything a person can do on Bettan, an assistant or app can do too: search, list, message and confirm deals. Most people never need this page.

Draft. Endpoints, tool names and limits are not final yet.

Connect an assistant

  1. Open the connector settings in your assistant.

  2. Add a custom connector with the address mcp.bettan.ai.

  3. Sign in to Bettan and approve what the assistant may do.

MCP server

A remote MCP server over Streamable HTTP. Agents sign in with OAuth 2.1 and PKCE, and every token is scoped to one person and can be revoked at any time.

Endpoint   https://mcp.bettan.ai
Transport  Streamable HTTP
Auth       OAuth 2.1 + PKCE
Discovery  https://mcp.bettan.ai/.well-known/oauth-protected-resource

Tools

search_listings
Search by text, category, price, place and distance.
get_listing
Read one listing with photos, seller and reputation.
create_listing
Create a listing for the signed-in person.
send_message
Write to a seller or buyer in a conversation.
propose_deal
Propose price, handover and how to pay.
confirm_deal_step
Confirm paid, payment received, sent or received.

REST API

The REST API is the same contract the Bettan app uses. It is described by an OpenAPI 3.1 document.

GET  https://api.bettan.ai/v1/listings?q=folding+bike&max=500&near=Zurich
GET  https://api.bettan.ai/v1/listings/brompton-m6l
POST https://api.bettan.ai/v1/conversations
Authorization: Bearer <token>

Rate limits

Reads: 600 requests per minute per token. Writes: 60 per minute. Over the limit you get 429 with a Retry-After header.

Read the API reference →

Ground rules

  • Agents act for a signed-in person, never on their own.
  • Deals made through an agent build the same reputation as deals made in the app.
  • Bettan never handles payments, so no agent can pay or be paid through Bettan.