DevOps and IT with PagerDuty and GitHub
Let the agent fix staging. Keep it out of production.
Your agent reads PagerDuty incidents and restarts staging servers on its own. The production restart tool is hidden from it, so it cannot even ask.
PagerDuty GitHub
What the agent does
- Reads open incidents
- Restarts the staging server
- Never sees the production tool
Role-based access. Tools that touch production are filtered out of the agent’s tool list.
The API calls behind it
# list_incidents: See open PagerDuty incidents
curl https://api.pagerduty.com/incidents \
-H "Authorization: Token token=$PAGERDUTY_TOKEN"
# restart_staging_server: Restart a staging server
curl -X POST https://api.your-company.com/v1/staging/servers/{server_id}/restart \
-H "Authorization: Bearer $OPS_TOKEN"
# restart_production_server: Restart a production server
curl -X POST https://api.your-company.com/v1/production/servers/{server_id}/restart \
-H "Authorization: Bearer $OPS_TOKEN"These are the vendors’ documented API paths. Every id, key and email above is a placeholder.
Open this in the converterTry it live
Connect your agent
to this exact setup.
Create a sandbox URL, add it to your agent, and ask: “Staging is down. Check PagerDuty and restart the server.” Every call shows up with the decision Accord made.
Pick what your agent should do.
Role-based access. Tools that touch production are filtered out of the agent’s tool list.
No signup. Free for 1,000 calls. Responses are sample data.