Runnable examples

Run Daptin through complete request flows.

Each repository configures Daptin, sends real requests, and checks both successful responses and expected rejections.

Start with the server →
OAuth 2.0 + OpenID Connect

Use Daptin as an OAuth 2.0 and OIDC provider.

Register a client, complete authorization code with PKCE, obtain tokens, and read the signed-in user. The test covers invalid redirect URLs and expired or reused authorization codes.

Run the OAuth provider demo ↗
Per-user credentials

Use a separate provider credential for each user.

Store OAuth or API credentials for each user and execute an installed operation with the matching secret. The demo verifies that one signed-in user cannot use another user's credential.

Run the integration-auth demo ↗
Usage, quotas, and credits

Enforce usage limits and credit balances.

Record ordinary API calls and model tokens, apply a quota, reject excess requests, debit a credit wallet, and keep the resulting usage and debit records.

Run the metering demo ↗
OpenAI-compatible API

Use the OpenAI SDK against Daptin.

Point the official OpenAI SDK at Daptin. Exercise model listing, chat, streaming, completions, embeddings, tool calls, usage fields, and structured errors.

Run the LLM demo ↗

Older schema examples

Use these files as syntax references.

The schema-samples repository contains YAML and JSON definitions for blogs, FAQs, stores, payments, transactions, and todos. Its latest published changes are from 2020, so treat it as a syntax reference and compare each model with the current schema documentation before starting a new application.

Browse schema samples ↗Read current schema documentation ↗

Writing an example

What a useful example should show.

Use a clean instance

Pin the Daptin version and start with an empty database so setup steps remain visible.

Name the failure

Test another user's credential, an exhausted quota, an invalid redirect URL, or a denied record.

Inspect the records

Show the request, the response, and the usage, permission, token, or audit record it created.

Keep it runnable

Document one command that starts dependencies and one command that exercises the main path.

Verified behavior

What the current demos verify.

The OAuth demo shows issued codes and tokens. The integration demo proves which user owns a credential. The metering demo shows usage, quota, credit, and debit records. The LLM demo compares streaming and non-streaming responses through the same OpenAI-compatible address.

Read the repository tests when you need the exact assertion. Copy the setup into a disposable environment before adapting it to application data.

Repository selection

Why only these repositories are listed.

This page omits old frontend starters, retired dashboard code, infrastructure forks, and experiments that no longer represent the product. The Daptin organization still preserves those repositories for people researching project history.

A complete application will appear here only when its setup is repeatable against a current release, its main path is covered by tests, and its interface demonstrates Daptin work that the focused repositories do not already prove.

Browse the full organization directory ↗

Run a demo against a clean Daptin instance.