Workflow integration
Connect issue trackers, CI signals, repository context, review queues, or release handoff systems.
API access
Request API access around one engineering workflow.
AgentFoundry API access starts with the real workflow you want to connect: the integration target, urgency, desired outcome, approval rules, and results your team needs before trusting an agent run.
Access principle
Integrations should preserve control.
API requests should name the systems involved, allowed actions, review checkpoints, data constraints, and report format needed for accountable human approval.
Common requests
Useful API requests are specific about the job and limits.
The API path is for teams that already know an integration or automation boundary matters. If the right first job is unclear, use contact instead.
Run records
Request structured run records, review notes, approval status, and audit-friendly delivery data.
Controlled actions
Define which tools, repos, checks, credentials, and deployment steps agents may use under human approval.
Pilot evaluation
Use the API request to explain the workflow, urgency, desired outcome, and results needed before broader access.
API request capture
Share the workflow, systems, urgency, and approval rules.
Choose “API access request” in the form and include the integration target, expected calls or events, desired outcome, constraints, and results your team needs to review.