Build on Fretie.
A REST API for quotes, rates, inbox, and customers; an email ingestion webhook; and a remote MCP server so AI agents can use Fretie natively. Everything below is machine-readable first.
Quickstart
Get a token
Machine clients use the OAuth 2.0 client-credentials grant. Credentials are issued per organization in the workspace settings (or by the org you're integrating with). Request only the scopes you need — they're listed in the OpenAPI security scheme.
curl -X POST https://api.fretie.com/auth/token \
-H "Content-Type: application/json" \
-d '{"client_id":"<your id>","client_secret":"<your secret>"}'Call the API
Send the token as a bearer header. All endpoints, parameters, and response schemas are described in /openapi.json, with a unique operationId on every operation for function-calling agents.
curl https://api.fretie.com/quotes \ -H "Authorization: Bearer <access_token>"
Push emails in
The ingestion webhook accepts raw emails from any system that can speak HTTP. Recognized quote requests run through the autopilot pipeline automatically and come back as priced draft quotes.
curl -X POST https://api.fretie.com/ingest/email \
-H "Authorization: Bearer <connector key>" \
-H "Content-Type: application/json" \
-d '{"from_email":"ops@customer.com","subject":"Rate needed — 2x40HC Shanghai→Rotterdam","body":"..."}'For AI agents: MCP first
Claude, ChatGPT, and other MCP clients should connect to the remote MCP server at https://mcp.fretie.com/mcp (Streamable HTTP). The server requires OAuth 2.1 and advertises its authorization server via RFC 9728 protected-resource metadata, so a compliant client can complete the whole flow from the 401 challenge alone. Tools cover quotes, rate search, inbox, and reconciliation, scoped to the authorized organization.
Every page on this site is also available as clean markdown — send Accept: text/markdown to any URL, or start from /llms.txt.
Machine-readable resources
OpenAPI spec
/openapi.json
Machine-readable description of every public endpoint, with operation ids, schemas, and OAuth scopes.
Agent auth guide (auth.md)
/auth.md
How agents authenticate: OAuth 2.1 via WorkOS AuthKit, client-credentials tokens, and API keys.
OAuth server metadata
/.well-known/oauth-authorization-server
RFC 8414 authorization-server metadata for the OAuth 2.0 flow.
API catalog
/.well-known/api-catalog
RFC 9727 linkset pointing at the API, its spec, and the MCP server.
MCP server card
/.well-known/mcp/server-card.json
Connection details for the Fretie MCP server (Streamable HTTP + OAuth).
llms.txt
/llms.txt
Agent-facing site overview with markdown links for every page.
API keys and M2M credentials are issued per organization inside the app (Settings → Developers) — sign in at app.fretie.com. The 14-day trial includes API access. Questions: contact@fretie.com.