Resources for app developers

Use this hub to navigate the core docs: API integration, safety constraints, standard definitions, and measured engineering evidence.

Building first? Jump straight to the API reference.

Start here

Browse

CORE

API reference

API reference, runtime concepts, endpoint docs, and integration patterns.

Open
SUPPORT

Contact

Talk through rollout constraints, integration fit, and production readiness.

Open
SECURITY

Safety

Runtime boundaries, consent controls, fail-closed behavior, and proof model.

Open
OVERVIEW

How wavebird works

The request flow and what runs where during ad-funded AI responses.

Open
GUIDE

Free tier economics

Model the cost and revenue math behind free AI usage.

Open
GUIDE

AI monetization

Compare practical monetization models for GenAI apps.

Open
GLOSSARY

wavebird

Canonical definition of wavebird and what the infrastructure does.

Open
GLOSSARY

GenAI app

Definition of the AI app surfaces wavebird supports.

Open
GLOSSARY

Inference-time ads

How ads can appear around the wait window while the answer loads.

Open
GLOSSARY

Data firewall

The boundary that keeps prompts and chat history out of ad delivery.

Open
GLOSSARY

OpenRTB

How the standard ad auction protocol relates to configured partner paths.

Open
STANDARD

Compute Sponsoring

The Compute Sponsoring proposal and its consent/data boundaries.

Open
WHITEPAPER

Proof integrity

Signed proof, beacon chains, Merkle roots, and verification model.

Open
STANDARD

Compute Sponsoring explained

The public Compute Sponsoring proposal and reference material.

Open
STANDARD

Compute Sponsoring v1.0 white paper

The public Compute Sponsoring proposal and reference material.

Open
EVIDENCE

Engineering evidence

Engineering evidence, benchmark results, and validation scope.

Open
WHITEPAPER

Proof integrity whitepaper

Signed proof, beacon chains, Merkle roots, and verification model.

Open
EVIDENCE

DPIA / DSFA

Public DPIA / DSFA for privacy boundaries and residual risk.

Open

Recommended path

Build with the Server API.

Use the API path when you want control over request timing, privacy boundaries, and rendering in your own UI.