Direct API / custom
Integration · Maximum control for bespoke tooling and custom workflows
At a glance
| Pricing | BYO API key |
| Setup effort | High |
| Open source | No |
| Interface | API/SDK |
| Privacy | Configurable |
| Model choice | BYO model |
| Compatibility | Anywhere you wire it |
What Direct API / custom does
—
Best for
Maximum control for bespoke tooling and custom workflows
Works well with
LLM Provider / Model
Agent / Orchestration
Conflicts & caveats
- Cursor Mobile only runs Cursor-managed agents and background tasks — local-only integrations like Direct API / custom cannot run on the phone.
- @codebase (Cursor) only works with Cursor built-in integration (yours is Direct API / custom).
- Continue's codebase indexing only works when the integration is Continue.dev (yours is Direct API / custom).
- Windsurf codebase indexing only works with Windsurf Cascade integration (yours is Direct API / custom).
- Aider architect mode requires the Aider integration (yours is Direct API / custom).
Build a full stack around Direct API / custom — Flowpicker shows compatibility warnings before you commit.
Open the stack planner →