Skip to main content
This walkthrough takes you from a Project API key to an agent that has created a file and reported back. You need:
  • a Project API key and the API base URL, from your administrator (Issue a Project API key);
  • a ready node or E2B backend, so Core has somewhere to run the agent (Nodes);
  • Python 3.9 or newer;
  • a model: the installation’s default model, or your own provider’s model ID, base URL and API key. Model execution says which one a Session uses and which protocols each harness speaks.
The example uses Codex, whose model provider must speak the OpenAI Responses API.

1. Connect

Core serves the OpenAI Agents API, so the official OpenAI SDK works unchanged. It reads two environment variables:
Check access. This runs no model and creates no sandbox:
An empty list means you are connected. The same check with curl:

2. Start a Session

A Session is one agent conversation with its own workspace. With openai_hosted, Core creates a sandbox for it on a node or E2B and starts the harness inside. With the installation’s default model, skip this. To use your own provider:
This makes a real model request and may incur charges.
  • x_agents_core holds Core’s additions to the OpenAI API; see Core extensions.
  • Keep the whole agent object in extra_body. SDK 3.13.0 replaces a body field with the matching extra_body field instead of merging them.

3. Wait for the result

A Session ID confirms creation, not success. Poll durable state; never resubmit to “retry”:
Success is a completed Turn whose Items describe the new file. A timeout neither cancels the work nor proves it failed.

Next steps