Your first API request
Create a project, choose least-privilege scopes, issue a sandbox key that is shown once and call the status endpoint.
Continue learning ›Clarity Developer Learn
From first request to reviewed tool.
More than code examples. Every learning path connects technical setup, the safety boundary, failure modes and an evidenced next step.
Start here
Three foundations. One secure workspace.
The sandbox is real and deliberately constrained. It provides projects, expiring keys, documented operations and server-confirmed usage — no hidden production rights.
Developer Apps
Structure redirects, environments and project boundaries so credentials never reach the client.
Continue learning ›Tool Builder
Design a clarity.tool/v1 manifest, declare C0–C2, validate it server-side and submit it for human review.
Continue learning ›Guided tutorials
Learn from real contracts.
Four executable, reproducible guides connect implementation, security review and an unambiguous finish line.
15 minutes · Guide
Sandbox Architecture
From an approved Audecius Account to the first observable request.
Open guide ›
24 minutes · Guide
Tool Design & Review
Design, validate and submit a declarative Clarity Tool for human review.
Open guide ›
20 minutes · Guide
AI with Oversight
Constrain AI features so their source, effect and human decision remain visible.
Open guide ›
18 minutes · Guide
Integration Readiness
Reproducibly test webhook signatures, idempotency, retries and release boundaries.
Open guide ›Developer Support
When the documentation is not enough.
Developer questions use the same traceable support path as Clarity. Category, project context and language stay with the case; sensitive secrets never belong in the message.
Start Developer Support ›