Your first Cedar workflow

Start with a text or JSON workflow for caller integration. You bring provider keys; your backend controls caller identity and usage allowances.

Cedar reserves a conservative maximum before each caller run. Your usage allowance must cover that full hold. Caller image output and paid xAI search return 409 until verified spending profiles exist, although admin testing retains those capabilities. Concurrent requests share the available quota. Holds settle or release automatically; abandoned holds expire after 15 minutes.

1. Create an application and assign a provider key.
2. Create a workflow manually. Set a supported model, instructions and optional JSON schema. Copy the authoring prompt if you want help drafting externally.
3. Save and test the workflow. Saving updates its live configuration.
4. Create an access key and usage plan. Store the key on your backend, and derive the external caller ID from your authenticated user.
5. Open the workflow integration instructions. Register the caller, start a run and poll the returned run ID until it reaches a terminal state. Retry status checks after connection errors instead of submitting again.
6. Check the returned result and Logs. Setup completes after a successful caller-scoped API run.

Native and browser apps call their own authenticated backend. Never ship a Cedar access key in client code.