ChatGPT
Cursor
Xero
Salesforce
Workday
Google Drive
Slack
Gmail
Notion
Asana
via Claude Code
SAP S/4HANA
200 OKClean
- User / Agent
- Taylor Brooks
via Copilot - Account
- Supplier Admins
Policies evaluated2
Restrict supplier changesNo match
1 other policyNo match
Supplier returned
AI Connector Builder. Any API, ready for your agents.
Turn an internal system, a niche SaaS tool or a customer's custom fields into tested actions your agents call over MCP, the AI SDKs or the Actions API.
Claude Code /connector:full brightwell from docs.brightwell.example/openapi.json
stackone-agent-harness · research, build, validate, each closed by a scripted gate
- Research 38 endpoints, 6 resources, v3 is current gate passed
- Auth OAuth 2.0 client credentials, token request works gate passed
- Build 24 actions in 6 partial files gate passed
- Validate 24 of 24 match the docs, stackone validate passes gate passed
test it on our staging account, then publish
- Test 24 of 24 actions pass on a real account 1 fixed, re-run
- Publish brightwell v1.0.0 pushed to your project
Companies already connected through StackOne
Two ways to build, or ask us. Your agent or ours, on the same engine.
Build in Claude Code with StackOne's skills and tools, or ask StackOne's agent in the dashboard. Both run the same steps and write the same YAML. Or have StackOne's team build it for you.
- Runs in your terminal
Bring your own agent
One command gives Claude Code StackOne's research, versioning and testing tools, plus the skills and slash commands that run a build. Then ask for a connector by name, or point it at the docs.
StackOne CLI docs (opens in a new tab) Build your first connector (opens in a new tab)
-
Runs on StackOneUse StackOne's agent
Ask in the dashboard chat, to build a connector or change one you have. StackOne's agent runs the same build on our side, with nothing to install and no model bill, and asks before it touches a real account or publishes.
-
Built by StackOne's team
Ask StackOne to build it
Request the connector and StackOne's team builds and maintains it. Typically days, once you give us API access. Fork it afterwards if you want to change it yourself.
The AI Connector Builder is part of the Team and Enterprise plans, and OEM Enterprise. Each connector you build or change and keep active uses one custom connector slot.
How a build works. Five steps, and a script decides when each one is done.
Each step closes only when its scripted check passes, never on the model's own say. Pick a step to see the tools it called and what it wrote, and switch agents: the build is the same.
Build a connector for our shipments API. The spec is at docs.brightwell.example/openapi.json
StackOne agent Your agent Claude Code
On it. I'll start with your OpenAPI spec.
Yours to change. The connector is YAML in your project: edit it, version it and check it in CI.
Brightwell Shipments connector
- OpenAPI 3.1
- 6 resources
- OAuth 2.0
- client credentials
- list_shipments
- get_shipment
- create_shipment
- list_rates
- list_carriers
- list_invoices
- validated
- staging account
- v1.0.0
AI Connector Builder Brightwell Shipments brightwell
stackone-agent-harness Same skills and tools in both agents.Research
/connector:full brightwell
scope: shipments, carriers, rates, invoices, webhooks, users
map_provider_key
brightwell · not in the catalogue, new connector
extract_oas_actions
docs.brightwell.example/openapi.json · 38 endpoints
analyze_versioning
v3 is current
resource-endpoint-fetcher × 6
parameters and responses for every endpoint
research brightwell
- read docs.brightwell.example · OpenAPI 3.1
- auth OAuth 2.0 client credentials
- base https://api.brightwell.example/v3
- pages cursor, up to 200 per page
- scope shipments, carriers, rates, invoices, webhooks, users
Auth first
vector_search
OAuth 2.0 client credentials · /oauth/token
Skill(build-connector)
authentication
stackone run
token request · 200
write authentication
brightwell.
authentication: - oauth2: type: oauth2 label: OAuth 2.0 grantType: client_credentials authorization: type: bearer token: $.credentials.accessTokenBuild
/connector:build
6 partial files, one per resource
Skill(connector-patterns)
cursor pagination · error mapping
Skill(build-connector)
list_shipments · get_shipment · create_shipment · list_rates · list_carriers · list_invoices
Skill(improve-descriptions)
24 action descriptions
write list_shipments
brightwell.
- actionId: list_shipments effects: [ read ] steps: - stepFunction: functionName: paginated_request parameters: url: /shipments method: get response: { dataKey: data, nextKey: next_cursor }Validate
/connector:validate
schema review and docs comparison
schema-reviewer
24 of 24 actions pass
provider-comparator × 6
every action matches the live docs
stackone validate
0 errors
validate brightwell
| schema review | 24 of 24 |
|---|---|
| docs comparison | 24 of 24 |
| stackone validate | 0 errors |
Test and publish
Skill(test-connector)
24 actions × 1 auth type · staging account
stackone run
list_rates · 400 · missing origin_postcode
Skill(build-connector)
fix: origin_postcode is required
Skill(scramble-credentials)
no plaintext credentials in the project
stackone push
brightwell v1.0.0
test all actions · staging account
| list_shipments | 200 · 50 rows |
|---|---|
| get_shipment | 200 |
| list_rates | 400 · missing origin_postcode |
| fix: origin_postcode is required | |
| list_rates | 200 |
| create_shipment | 201 · removed after the test |
| stackone push | v1.0.0 |
AI Connector Builder demo. Watch a build from prompt to connector.
Change a connector that exists. Fit any connector to a customer's setup.
Most builds start from a connector that already works. Pull it, ask for the change, and push your version.
-
Pull it
Any StackOne connector, or one you built, comes down as YAML you can read.
-
Ask for the change
A customer's custom objects, a field they renamed, an action StackOne doesn't ship. Claude Code or StackOne's agent writes it the way the rest of the connector is written.
-
Check it and push
Validate it, run it on the customer's account, and push. It goes out as a new version for your project, and nobody else's connector changes.
- Customizing connectors in the docs (opens in a new tab)
Terminal
# Start from StackOne's Workday connector
stackone pull --connector workday --profile production
# Ask your agent for the change, then check and try it
cd connectors/workday
stackone validate .
stackone run --profile production \
--connector workday.connector.s1.yaml \
--account-id <customer account> --action-id <action id>
stackone push . --profile productionWhat you get. YAML you own, served to every agent.
A build leaves files in your project, not a black box. Publish them from your laptop or your CI, and every agent and app you run can call them.
Your files
brightwell.connector.s1.yamlbrightwell.shipments.s1.partial.yamlbrightwell.rates.s1.partial.yamlbrightwell.invoices.s1.partial.yaml- and 3 more partial files
YAML you read, review and keep in Git.
Your project
brightwellv1.1.0brightwellv1.0.0
Each push is a new version. Validate on every pull request and publish on merge with GitHub Actions (opens in a new tab).
Your agents and apps
- MCPAny MCP client, through the Tool Gateway
- AI SDKs (opens in a new tab)TypeScript and Python, for tool calling
- Actions API (opens in a new tab)One RPC call from your backend
Every connector runs on the Agent Execution Engine, which handles sign-in, token refresh, pagination, retries and rate limits, with the same tool policies and request logs as StackOne's own connectors.
The AI Connector Builder works with the rest of StackOne
- 01 / 05
Agent Execution Engine
Runs every connector you build, with the provider's sign-in, pagination and retries built in.
- 02 / 05
Pre-built connectors
640+ connectors StackOne builds and maintains, ready to pull and change.
- 03 / 05
Tool Gateway MCP
One MCP URL for any AI client, serving your connectors beside StackOne's.
- 04 / 05
Tool Policies
Decide which actions of each connector an agent may call.
- 05 / 05
Observability & Audit
See every action your agents ran, on every connector.
FAQ. Questions about the AI Connector Builder
Build the connector your agents are missing.
Book a demo to watch a build on an API you choose, or start free and explore StackOne's connectors.