Services and endpoints

Services

A service is registered by a developer and represents an AI-powered service (e.g. API, MCP server). The service has metadata (name, description), a backend URL where the gateway forwards requests, and billing/usage configuration. Service keys are scoped to a service and are used to invoke that service.

Endpoints

Each service can expose one or more endpoints. Callers invoke a specific endpoint via the gateway using the path /api/service/{serviceId}/endpoint/{endpointId}/invoke (or the equivalent path for your deployment). The gateway forwards the request to your backend with HMAC-signed headers and optional body; you verify the signature, process the request, and optionally report usage or send progress/completion for async flows.

See API overview (Gateway) for invoke details and Request signing (HMAC) for backend verification.

Backend target URLs (registration)

When you register endpoints in the dashboard, you provide the full URL to your service, including the path. For dynamic path segments, use curly-brace placeholders in the URL path—for example https://api.yourservice.com/orders/{id}—so the platform can match subscriber traffic to the correct operation. That lines up with how paths appear on branded API hosts and with OpenAPI import when you use specs.