API integrations and tools

Use this page when the main problem is API wiring, tool calling, browsing integration, SDK usage, or external system integration.

Map workflow placement for API systems

Use this when stable rules, reference material, retrieval, or runtime prompts need to be placed in an API architecture.

Use with:
Open reference →
Run the standards-backed implementation review

Use this when implementation must be checked against official framework, runtime, API, or platform guidance.

Use with:
Open guide →
Run the engineering quality gate

Use this when an integration change needs broader quality review.

Use with:
Open guide →
Request web browsing

Use this when a tool or API workflow depends on current public information.

Use with:
Open guide →

When to use API integrations and tools

Use this page when the work is not just chat prompting but integration with an API, SDK, connector, retrieval layer, tool, or external service.
Use it when correctness depends on tool parameters, auth boundaries, web access, storage, retrieval, or runtime validation.
Use it when implementation needs to be checked against official vendor or platform documentation.

Before you start

Know which API, SDK, tool, connector, or external system is involved.
Know whether the integration reads data, writes data, calls tools, retrieves documents, or changes external state.
Have official vendor documentation available when reviewing implementation correctness.

Prompt engineering
The main problem is prompt wording, instruction structure, or reusable prompt design.
AI assistants
The main problem is assistant-product behavior rather than custom integration.
Agents and workflows
The main problem is orchestration, routing, or multi-step agent behavior.