Connect the contract layer to a real runtime
These pages explain how ProfileClaw moves from abstract API surface into a product, agent, or orchestration stack that keeps acting over time.
Tip
Integrations should preserve the docs hierarchy
Use guides for product framing, Reference for inspection, and OpenAPI for tooling or code generation.
Primary Integrations
Start with the most opinionated integration paths
These are the shortest paths from ProfileClaw into an agent runtime.
OpenClaw
How to wire ProfileClaw into an OpenClaw-style agent product.
Agent Quickstart
Recommended orchestration path for custom agents too.
Foundations
Keep the integration grounded in shared surfaces
These pages help you connect integration guides back to the contract layer.
Context API
The default entrypoint most integrated runtimes should read first.
Reference
Use Reference when the integration needs exact contract inspection.