Architecture and API budget
Architecture and API budget — OpenAI tools and agents without paid execution. Responses and agent runtimes; Subscription and API credit balance; Label test fragments explicitly. Practical assignment: Practice: Architecture and API budget.
Demo edition. The materials are undergoing editorial review.
Topics covered
- Responses and agent runtimes
- Subscription and API credit balance
- Label test fragments explicitly
Responses and agent runtimes
Responses returns model output and proposed tool calls while your application controls processing, permissions and custom function execution. Agents SDK adds a runner, tools and resumable state inside your runtime. Managed Agents API is another option with a separate lifecycle. This course builds an offline harness around documented Responses-shaped fragments and explains SDK approvals without invoking run or an API. The educational agent reads an allowed operational note and proposes a structured recommendation, never administering a real VPS or changing accounts.
Subscription and API credit balance
Current official guidance lets eligible Pro/Business subscriptions separately claim API credit benefits for an owned API organization. This is neither automatic access for every plan nor unlimited API usage. Credits have eligibility, expiry and organization rules; included ChatGPT/Codex allowances are different limits. Usage can continue against purchased credits after free credits expire or run out. This course activates nothing, creates no keys and invokes no API even when a benefit exists. Offline fixtures, rather than assumptions about your account, enforce the zero-spend exercise.
Label test fragments explicitly
Create offline-agent-lab containing tools.mjs, loop.mjs, output.mjs, approval.mjs and eval.test.mjs. Fixtures include only the documented fields needed by tests, not purported full responses from a real server. Label offline mode and invent no usage, request IDs or latency. This tests parsing, routing and permission boundaries without inference. A later provider integration must separately establish model compatibility, SDK version, full response lifecycle and budget; offline success does not automatically prove any of those properties.
Practical assignment
Practice: Architecture and API budget
Continue to learning