Skip to content

API Address

mavrovde edited this page Nov 1, 2026 · 2 revisions

API Address

The public address of ViaFrei API: why it gets its own subdomain, and what that costs.

Decision

Address https://api.viafrei.de
Versioning in the path: https://api.viafrei.de/v1/...
Status Recommended. Becomes due with the first deployment, after the stack decision ([[Stack Comparison

Why a subdomain

  • Separate edge rules. Rate limits, CORS, caching and request size limits for the API are set on their own, never mixed with the website's or the MCP server's.
  • Cookie isolation. The API never receives the website's cookies or consent state. It authenticates with API keys only.
  • Freedom to move. The API can later move to its own server or behind a CDN with a DNS change, without touching the website.
  • Clarity for users. It mirrors mcp.viafrei.de, so keys, documentation and status pages are easy to tell apart.

Alternative considered

A path on the website, viafrei.de/api. It works, but it ties the API to the website's routing, limits and outages, and makes a later move harder. Not chosen.

Cost

One DNS record and one TLS certificate. The edge in front of ViaFrei issues and renews certificates automatically.

Related

Home

About

Design

Data Model

Technical specification

Testing

Engineering

Technology choice

Reference

Clone this wiki locally