Open-source and public first-party evidence

AI API integration examples

These pages describe integrations visible in first-party documentation or public repositories. They do not infer a private production stack, vendor spend, or revenue.

Public repository

Postiz

A source-linked reading of API integration surfaces visible in the public Postiz repository, without inferring its private production stack or revenue.

Read documented integration →
First-party documentation

Open WebUI

How Open WebUI documents connections to OpenAI-compatible endpoints, with an evidence boundary between supported configuration and real deployments.

Read documented integration →
First-party documentation

LibreChat

How LibreChat documents configurable AI endpoints, model routes, and the evidence a team should verify before choosing a production provider.

Read documented integration →
First-party documentation

Vercel AI SDK

A documented integration pattern for selecting and configuring model providers through the Vercel AI SDK, with explicit model and cost checks.

Read documented integration →
First-party documentation

LiteLLM

A first-party documented pattern for calling OpenRouter through LiteLLM while preserving model, provider route, usage, and cost identity.

Read documented integration →
First-party documentation

Continue

A documented configuration pattern for connecting Continue to OpenRouter and checking the selected model route, credentials, capabilities, and cost.

Read documented integration →
First-party documentation

Dify

How Dify documents model-provider configuration and what source, capability, limit, and cost evidence a team should collect before committing a workflow.

Read documented integration →
First-party documentation

n8n

A documented workflow integration for n8n and OpenAI, with a practical checklist for credentials, model identity, usage meters, retries, and cost.

Read documented integration →
First-party documentation

Flowise

A source-linked integration pattern for configuring an OpenAI chat model in Flowise and validating model identity, usage meters, retries, and workload cost.

Read documented integration →
First-party documentation

Langflow

How Langflow documents provider components and how to keep model, route, price, capability, and source-evidence boundaries explicit.

Read documented integration →