ancha.

Every tool your agent touches.

Replicas of the APIs your agent calls, each with its own data. Open one to see every endpoint it serves.

38replicas ready0in progress

Chat and email 5

SlackChannels, messages and threads Ready22 endpoints
API
Web API subset · HTTP
Resources
Channels, People, Messages
Starter data
10 members · 10 channels · 52 messages
Your agent gets
SLACK_API_URL SLACK_BOT_TOKEN SLACK_SIGNING_SECRET SLACK_APP_TOKEN
Tested with
@slack/bolt 5.1.0 @slack/web-api 7.19.0
Limits
Bot-token API subset; no general Slack workspace clone.
Explore the Slack test environment →

Endpoints 22

Slack in the docs →

apps 1

  • POST/api/apps.connections.open

auth 1

  • POST/api/auth.test

chat 4

  • POST/api/chat.delete
  • POST/api/chat.getPermalink
  • POST/api/chat.postMessage
  • POST/api/chat.update

conversations 8

  • POST/api/conversations.create
  • POST/api/conversations.history
  • POST/api/conversations.info
  • POST/api/conversations.join
  • POST/api/conversations.list
  • POST/api/conversations.members
  • POST/api/conversations.open
  • POST/api/conversations.replies

reactions 3

  • POST/api/reactions.add
  • POST/api/reactions.get
  • POST/api/reactions.remove

search 1

  • POST/api/search.messages

users 4

  • POST/api/users.conversations
  • POST/api/users.info
  • POST/api/users.list
  • POST/api/users.lookupByEmail
GmailMailboxes, threads, labels and drafts Ready26 endpoints
API
v1 subset · HTTP
Resources
Messages, Threads, Labels, Drafts, History
Your agent gets
GMAIL_API_URL GMAIL_ACCESS_TOKEN
Tested with
@googleapis/gmail 22.0.2
Limits
Mail moves only inside the world: mail to a seeded mailbox is delivered, anything else is recorded in Sent. Common search operators; uploads, batch requests, push notifications, filters, settings and delegation are not modeled.

Endpoints 26

Gmail in the docs →

gmail 26

  • GET/gmail/v1/users/:userId/drafts
  • POST/gmail/v1/users/:userId/drafts
  • GET/gmail/v1/users/:userId/drafts/:id
  • PUT/gmail/v1/users/:userId/drafts/:id
  • DELETE/gmail/v1/users/:userId/drafts/:id
  • POST/gmail/v1/users/:userId/drafts/send
  • GET/gmail/v1/users/:userId/history
  • GET/gmail/v1/users/:userId/labels
  • POST/gmail/v1/users/:userId/labels
  • GET/gmail/v1/users/:userId/labels/:id
  • PATCH/gmail/v1/users/:userId/labels/:id
  • DELETE/gmail/v1/users/:userId/labels/:id
  • GET/gmail/v1/users/:userId/messages
  • GET/gmail/v1/users/:userId/messages/:id
  • POST/gmail/v1/users/:userId/messages/:id/modify
  • POST/gmail/v1/users/:userId/messages/:id/trash
  • POST/gmail/v1/users/:userId/messages/:id/untrash
  • GET/gmail/v1/users/:userId/messages/:messageId/attachments/:id
  • POST/gmail/v1/users/:userId/messages/batchModify
  • POST/gmail/v1/users/:userId/messages/send
  • GET/gmail/v1/users/:userId/profile
  • GET/gmail/v1/users/:userId/threads
  • GET/gmail/v1/users/:userId/threads/:id
  • POST/gmail/v1/users/:userId/threads/:id/modify
  • POST/gmail/v1/users/:userId/threads/:id/trash
  • POST/gmail/v1/users/:userId/threads/:id/untrash
ResendTransactional email, broadcasts, domains, contacts and segments Ready40 endpoints
API
REST subset · HTTP
Resources
Emails, Batch, Broadcasts, Domains, Contacts, Segments
Your agent gets
RESEND_BASE_URL RESEND_API_KEY
Tested with
resend 6.37.0
Limits
Mail is recorded, not delivered: bounced@ and complained@resend.dev give those outcomes, other recipients are delivered two simulated seconds after sending. Broadcasts go to the segment’s subscribed contacts as they are when the send is requested. Domain verification completes two simulated minutes after it is requested; templates, webhooks, topics and contact properties are gaps.

Endpoints 40

Resend in the docs →

audiences 8

  • GET/audiences
  • POST/audiences
  • GET/audiences/:id
  • DELETE/audiences/:id
  • GET/audiences/:id/contacts
  • POST/audiences/:id/contacts
  • GET/audiences/:id/contacts/:contact
  • PATCH/audiences/:id/contacts/:contact

broadcasts 7

  • GET/broadcasts
  • POST/broadcasts
  • GET/broadcasts/:id
  • PATCH/broadcasts/:id
  • DELETE/broadcasts/:id
  • POST/broadcasts/:id/cancel
  • POST/broadcasts/:id/send

contacts 8

  • GET/contacts
  • POST/contacts
  • GET/contacts/:id
  • PATCH/contacts/:id
  • DELETE/contacts/:id
  • GET/contacts/:id/segments
  • POST/contacts/:id/segments/:segment_id
  • DELETE/contacts/:id/segments/:segment_id

domains 5

  • GET/domains
  • POST/domains
  • GET/domains/:id
  • DELETE/domains/:id
  • POST/domains/:id/verify

emails 6

  • GET/emails
  • POST/emails
  • GET/emails/:id
  • PATCH/emails/:id
  • POST/emails/:id/cancel
  • POST/emails/batch

segments 6

  • GET/segments
  • POST/segments
  • GET/segments/:id
  • PATCH/segments/:id
  • DELETE/segments/:id
  • GET/segments/:id/contacts
TwilioSMS, voice calls, Verify codes and phone number lookups Ready20 endpoints
API
REST 2010-04-01, Verify v2 and Lookup v2 subset · HTTP
Resources
Messages, Calls, Phone numbers, Verify, Lookup, Balance
Your agent gets
TWILIO_API_URL TWILIO_ACCOUNT_SID TWILIO_AUTH_TOKEN
Tested with
twilio 6.2.0
Limits
The SDK always calls https://api.twilio.com, verify.twilio.com and lookups.twilio.com: give twilio() an httpClient (a RequestClient subclass) that sends https://api.twilio.com to TWILIO_API_URL and https://verify.twilio.com or https://lookups.twilio.com to TWILIO_API_URL plus /verify or /lookups. Nothing is sent: SMS status follows the scene clock and the world’s phone directory (landlines and unreachable phones come back undelivered, opted-out numbers are refused); calls play no audio; status callbacks are recorded, not called; Verify codes are in the ground truth. SMS and voice only: no MMS, WhatsApp, Messaging Services, Conversations, Studio or recordings; the account SID and auth token, not API keys.

Endpoints 20

Twilio in the docs →

2010-04-01 13

  • GET/2010-04-01/Accounts/{AccountSid}.json
  • GET/2010-04-01/Accounts/{AccountSid}/Balance.json
  • GET/2010-04-01/Accounts/{AccountSid}/Calls.json
  • POST/2010-04-01/Accounts/{AccountSid}/Calls.json
  • GET/2010-04-01/Accounts/{AccountSid}/Calls/{Sid}.json
  • POST/2010-04-01/Accounts/{AccountSid}/Calls/{Sid}.json
  • GET/2010-04-01/Accounts/{AccountSid}/IncomingPhoneNumbers.json
  • GET/2010-04-01/Accounts/{AccountSid}/IncomingPhoneNumbers/{Sid}.json
  • GET/2010-04-01/Accounts/{AccountSid}/Messages.json
  • POST/2010-04-01/Accounts/{AccountSid}/Messages.json
  • GET/2010-04-01/Accounts/{AccountSid}/Messages/{Sid}.json
  • POST/2010-04-01/Accounts/{AccountSid}/Messages/{Sid}.json
  • DELETE/2010-04-01/Accounts/{AccountSid}/Messages/{Sid}.json

lookups 1

  • GET/lookups/v2/PhoneNumbers/{PhoneNumber}

verify 6

  • GET/verify/v2/Services
  • GET/verify/v2/Services/{Sid}
  • POST/verify/v2/Services/{Sid}/VerificationCheck
  • POST/verify/v2/Services/{Sid}/Verifications
  • GET/verify/v2/Services/{Sid}/Verifications/{VerificationSid}
  • POST/verify/v2/Services/{Sid}/Verifications/{VerificationSid}
DiscordA community server as its bot sees it: channels, messages, threads and reactions Ready25 endpoints
API
REST API v10 subset · HTTP
Resources
Channels, Messages, Threads, Reactions, Pins, Members, Roles, DMs
Your agent gets
DISCORD_API_URL DISCORD_BOT_TOKEN
Limits
Send Authorization: Bot DISCORD_BOT_TOKEN to DISCORD_API_URL (it ends in /api/v10). Discord publishes no official Node client; the tests use the documented HTTP API. What the bot may read and send follows its role and each channel’s permission overwrites (Missing Access, Missing Permissions); IDs are snowflakes on the scene clock. REST only: no gateway events, slash commands, webhooks, attachments, components, polls or voice.

Endpoints 25

Discord in the docs →

channels 15

  • GET/api/v10/channels/{channel_id}
  • GET/api/v10/channels/{channel_id}/messages
  • POST/api/v10/channels/{channel_id}/messages
  • GET/api/v10/channels/{channel_id}/messages/{message_id}
  • PATCH/api/v10/channels/{channel_id}/messages/{message_id}
  • DELETE/api/v10/channels/{channel_id}/messages/{message_id}
  • GET/api/v10/channels/{channel_id}/messages/{message_id}/reactions/{emoji}
  • PUT/api/v10/channels/{channel_id}/messages/{message_id}/reactions/{emoji}/@me
  • DELETE/api/v10/channels/{channel_id}/messages/{message_id}/reactions/{emoji}/@me
  • POST/api/v10/channels/{channel_id}/messages/{message_id}/threads
  • GET/api/v10/channels/{channel_id}/pins
  • PUT/api/v10/channels/{channel_id}/pins/{message_id}
  • DELETE/api/v10/channels/{channel_id}/pins/{message_id}
  • POST/api/v10/channels/{channel_id}/threads
  • POST/api/v10/channels/{channel_id}/typing

guilds 6

  • GET/api/v10/guilds/{guild_id}
  • GET/api/v10/guilds/{guild_id}/channels
  • GET/api/v10/guilds/{guild_id}/members
  • GET/api/v10/guilds/{guild_id}/members/{user_id}
  • GET/api/v10/guilds/{guild_id}/roles
  • GET/api/v10/guilds/{guild_id}/threads/active

users 4

  • GET/api/v10/users/{user_id}
  • GET/api/v10/users/@me
  • POST/api/v10/users/@me/channels
  • GET/api/v10/users/@me/guilds

Code and issues 4

GitHubRepositories, pull requests and deployments Ready71 endpoints
API
REST subset · HTTP
Resources
Repositories, Commits, Pull requests, Deployments
Starter data
3 repositories · 7 pull requests · 11 issues · 10 commits
Your agent gets
GITHUB_API_URL GITHUB_TOKEN GITHUB_WEBHOOK_SECRET
Tested with
@octokit/rest 22.0.1
Limits
Selected repository and deployment operations.

Endpoints 71

GitHub in the docs →

actions 4

  • GET/repos/:owner/:repo/actions/runs
  • GET/repos/:owner/:repo/actions/runs/:id
  • POST/repos/:owner/:repo/actions/runs/:id/rerun
  • GET/repos/:owner/:repo/actions/workflows/:workflow/runs

branches 2

  • GET/repos/:owner/:repo/branches
  • GET/repos/:owner/:repo/branches/:branch

check-runs 1

  • GET/repos/:owner/:repo/check-runs/:id

commits 3

  • GET/repos/:owner/:repo/commits
  • GET/repos/:owner/:repo/commits/:ref
  • GET/repos/:owner/:repo/commits/:ref/check-runs

compare 1

  • GET/repos/:owner/:repo/compare/:base...:head

contents 2

  • PUT/repos/:owner/:repo/contents/:path
  • GET/repos/:owner/:repo/contents/:path?

deployments 6

  • GET/repos/:owner/:repo/deployments
  • POST/repos/:owner/:repo/deployments
  • GET/repos/:owner/:repo/deployments/:id
  • GET/repos/:owner/:repo/deployments/:id/statuses
  • POST/repos/:owner/:repo/deployments/:id/statuses
  • GET/repos/:owner/:repo/deployments/:id/statuses/:statusId

git 11

  • POST/repos/:owner/:repo/git/blobs
  • GET/repos/:owner/:repo/git/blobs/:sha
  • POST/repos/:owner/:repo/git/commits
  • GET/repos/:owner/:repo/git/commits/:sha
  • GET/repos/:owner/:repo/git/matching-refs/:ref?
  • GET/repos/:owner/:repo/git/ref/:ref
  • POST/repos/:owner/:repo/git/refs
  • PATCH/repos/:owner/:repo/git/refs/:ref
  • DELETE/repos/:owner/:repo/git/refs/:ref
  • POST/repos/:owner/:repo/git/trees
  • GET/repos/:owner/:repo/git/trees/:sha

issues 15

  • GET/repos/:owner/:repo/issues
  • POST/repos/:owner/:repo/issues
  • GET/repos/:owner/:repo/issues/:number
  • PATCH/repos/:owner/:repo/issues/:number
  • GET/repos/:owner/:repo/issues/:number/comments
  • POST/repos/:owner/:repo/issues/:number/comments
  • GET/repos/:owner/:repo/issues/:number/labels
  • POST/repos/:owner/:repo/issues/:number/labels
  • PUT/repos/:owner/:repo/issues/:number/labels
  • DELETE/repos/:owner/:repo/issues/:number/labels
  • DELETE/repos/:owner/:repo/issues/:number/labels/:name
  • GET/repos/:owner/:repo/issues/comments
  • GET/repos/:owner/:repo/issues/comments/:id
  • PATCH/repos/:owner/:repo/issues/comments/:id
  • DELETE/repos/:owner/:repo/issues/comments/:id

labels 5

  • GET/repos/:owner/:repo/labels
  • POST/repos/:owner/:repo/labels
  • GET/repos/:owner/:repo/labels/:name
  • PATCH/repos/:owner/:repo/labels/:name
  • DELETE/repos/:owner/:repo/labels/:name

orgs 1

  • GET/orgs/:org/repos

pulls 17

  • GET/repos/:owner/:repo/pulls
  • POST/repos/:owner/:repo/pulls
  • GET/repos/:owner/:repo/pulls/:number
  • PATCH/repos/:owner/:repo/pulls/:number
  • GET/repos/:owner/:repo/pulls/:number/comments
  • POST/repos/:owner/:repo/pulls/:number/comments
  • GET/repos/:owner/:repo/pulls/:number/commits
  • GET/repos/:owner/:repo/pulls/:number/files
  • GET/repos/:owner/:repo/pulls/:number/merge
  • PUT/repos/:owner/:repo/pulls/:number/merge
  • GET/repos/:owner/:repo/pulls/:number/reviews
  • POST/repos/:owner/:repo/pulls/:number/reviews
  • GET/repos/:owner/:repo/pulls/:number/reviews/:id
  • GET/repos/:owner/:repo/pulls/comments
  • GET/repos/:owner/:repo/pulls/comments/:id
  • PATCH/repos/:owner/:repo/pulls/comments/:id
  • DELETE/repos/:owner/:repo/pulls/comments/:id

repos 1

  • GET/repos/:owner/:repo

user 2

  • GET/user
  • GET/user/repos
LinearIssues, projects and team workflows Ready27 endpoints
API
GraphQL subset · HTTP
Resources
Issues, Comments, Teams, Workflow states, Labels, Projects, Users
Your agent gets
LINEAR_API_URL LINEAR_API_KEY
Tested with
@linear/sdk 100.0.0
Limits
Linear's published schema, pruned to the operations served; other fields and types answer as coverage gaps. No cycles, initiatives, documents, attachments, notifications, webhooks or sorting; filters cover the common comparators. @linear/sdk accepts a plain-http apiUrl only on localhost, 127.0.0.1 or [::1]; elsewhere the endpoint needs TLS.

Endpoints 27

Linear in the docs →

comment 1

  • QUERYcomment

commentCreate 1

  • MUTATIONcommentCreate

commentDelete 1

  • MUTATIONcommentDelete

comments 1

  • QUERYcomments

commentUpdate 1

  • MUTATIONcommentUpdate

issue 1

  • QUERYissue

issueAddLabel 1

  • MUTATIONissueAddLabel

issueArchive 1

  • MUTATIONissueArchive

issueCreate 1

  • MUTATIONissueCreate

issueDelete 1

  • MUTATIONissueDelete

issueLabel 1

  • QUERYissueLabel

issueLabelCreate 1

  • MUTATIONissueLabelCreate

issueLabels 1

  • QUERYissueLabels

issueRemoveLabel 1

  • MUTATIONissueRemoveLabel

issues 1

  • QUERYissues

issueUpdate 1

  • MUTATIONissueUpdate

organization 1

  • QUERYorganization

project 1

  • QUERYproject

projects 1

  • QUERYprojects

searchIssues 1

  • QUERYsearchIssues

team 1

  • QUERYteam

teams 1

  • QUERYteams

user 1

  • QUERYuser

users 1

  • QUERYusers

viewer 1

  • QUERYviewer

workflowState 1

  • QUERYworkflowState

workflowStates 1

  • QUERYworkflowStates
JiraIssues, JQL search, comments, transitions and sprints Ready57 endpoints
API
REST v3/v2 and agile 1.0 subset · HTTP
Resources
Projects, Issues, Comments, Transitions, Search, Users, Boards, Sprints
Your agent gets
JIRA_BASE_URL JIRA_EMAIL JIRA_API_TOKEN
Limits
Atlassian publishes no official JavaScript client: call ${JIRA_BASE_URL}/rest/api/3/... with HTTP Basic (JIRA_EMAIL and JIRA_API_TOKEN). /rest/api/3/search is gone, as on live Jira; /search/jql returns only issue ids unless fields are requested. Team-managed projects with the simplified workflow (To Do, In Progress, In Review, Done). Attachments, worklogs, webhooks, sprint changes and JQL history operators are gaps.

Endpoints 57

Jira in the docs →

agile 11

  • POST/rest/agile/1.0/backlog/issue
  • GET/rest/agile/1.0/board
  • GET/rest/agile/1.0/board/:id
  • GET/rest/agile/1.0/board/:id/backlog
  • GET/rest/agile/1.0/board/:id/issue
  • GET/rest/agile/1.0/board/:id/sprint
  • POST/rest/agile/1.0/sprint
  • GET/rest/agile/1.0/sprint/:id
  • POST/rest/agile/1.0/sprint/:id
  • GET/rest/agile/1.0/sprint/:id/issue
  • POST/rest/agile/1.0/sprint/:id/issue

api 46

  • GET/rest/api/3/field
  • POST/rest/api/3/issue
  • GET/rest/api/3/issue/:key
  • PUT/rest/api/3/issue/:key
  • DELETE/rest/api/3/issue/:key
  • PUT/rest/api/3/issue/:key/assignee
  • GET/rest/api/3/issue/:key/changelog
  • GET/rest/api/3/issue/:key/comment
  • POST/rest/api/3/issue/:key/comment
  • GET/rest/api/3/issue/:key/comment/:id
  • PUT/rest/api/3/issue/:key/comment/:id
  • DELETE/rest/api/3/issue/:key/comment/:id
  • GET/rest/api/3/issue/:key/transitions
  • POST/rest/api/3/issue/:key/transitions
  • GET/rest/api/3/issue/:key/watchers
  • POST/rest/api/3/issue/:key/watchers
  • DELETE/rest/api/3/issue/:key/watchers
  • POST/rest/api/3/issue/bulk
  • GET/rest/api/3/issue/createmeta/:key/issuetypes
  • GET/rest/api/3/issue/createmeta/:key/issuetypes/:type
  • POST/rest/api/3/issueLink
  • GET/rest/api/3/issueLink/:id
  • DELETE/rest/api/3/issueLink/:id
  • GET/rest/api/3/issueLinkType
  • GET/rest/api/3/issuetype
  • GET/rest/api/3/label
  • GET/rest/api/3/myself
  • GET/rest/api/3/priority
  • GET/rest/api/3/project
  • GET/rest/api/3/project/:key
  • GET/rest/api/3/project/:key/components
  • GET/rest/api/3/project/:key/statuses
  • GET/rest/api/3/project/:key/versions
  • GET/rest/api/3/project/search
  • GET/rest/api/3/resolution
  • GET/rest/api/3/search
  • POST/rest/api/3/search
  • POST/rest/api/3/search/approximate-count
  • GET/rest/api/3/search/jql
  • POST/rest/api/3/search/jql
  • GET/rest/api/3/serverInfo
  • GET/rest/api/3/status
  • GET/rest/api/3/statuscategory
  • GET/rest/api/3/user
  • GET/rest/api/3/user/assignable/search
  • GET/rest/api/3/user/search
AsanaProjects, sections, tasks, subtasks and comments Ready23 endpoints
API
REST API 1.0 subset · HTTP
Resources
Projects, Sections, Tasks, Subtasks, Comments, Search, Users
Your agent gets
ASANA_API_URL ASANA_ACCESS_TOKEN
Limits
Send ASANA_ACCESS_TOKEN as a Bearer token to ASANA_API_URL (it ends in /api/1.0); bodies are wrapped in {"data": …}. Asana publishes an official Node client (asana); these tests use the documented HTTP shapes. Lists return compact records unless opt_fields asks for more, and page with limit and offset; task search covers text, people, projects, sections, completion and dates. No tags, custom fields, portfolios, goals, teams, attachments, webhooks or events.

Endpoints 23

Asana in the docs →

1 23

  • GET/api/1.0/projects
  • GET/api/1.0/projects/{project_gid}
  • GET/api/1.0/projects/{project_gid}/sections
  • POST/api/1.0/projects/{project_gid}/sections
  • GET/api/1.0/projects/{project_gid}/tasks
  • POST/api/1.0/sections/{section_gid}/addTask
  • GET/api/1.0/sections/{section_gid}/tasks
  • GET/api/1.0/tasks
  • POST/api/1.0/tasks
  • GET/api/1.0/tasks/{task_gid}
  • PUT/api/1.0/tasks/{task_gid}
  • DELETE/api/1.0/tasks/{task_gid}
  • POST/api/1.0/tasks/{task_gid}/addProject
  • POST/api/1.0/tasks/{task_gid}/removeProject
  • GET/api/1.0/tasks/{task_gid}/stories
  • POST/api/1.0/tasks/{task_gid}/stories
  • GET/api/1.0/tasks/{task_gid}/subtasks
  • POST/api/1.0/tasks/{task_gid}/subtasks
  • GET/api/1.0/users
  • GET/api/1.0/users/{user_gid}
  • GET/api/1.0/workspaces
  • GET/api/1.0/workspaces/{workspace_gid}
  • GET/api/1.0/workspaces/{workspace_gid}/tasks/search

On-call 4

DatadogMonitors, metrics and logs Ready26 endpoints
API
v1 / v2 subset · HTTP
Resources
Monitors, Metrics, Logs, Dashboards
Starter data
7 monitors · 3 dashboards · 8 metrics · 17 log lines
Your agent gets
DATADOG_API_URL DD_API_KEY DD_APP_KEY DATADOG_WEBHOOK_TOKEN
Tested with
@datadog/datadog-api-client 1.64.0
Limits
Bounded query grammar and monitor behavior.

Endpoints 26

Datadog in the docs →

dashboard 2

  • GET/api/v1/dashboard
  • GET/api/v1/dashboard/:id

downtime 10

  • GET/api/v1/downtime
  • POST/api/v1/downtime
  • GET/api/v1/downtime/:id
  • PUT/api/v1/downtime/:id
  • DELETE/api/v1/downtime/:id
  • GET/api/v2/downtime
  • POST/api/v2/downtime
  • GET/api/v2/downtime/:id
  • PATCH/api/v2/downtime/:id
  • DELETE/api/v2/downtime/:id

events 2

  • GET/api/v1/events
  • POST/api/v1/events

incidents 4

  • GET/api/v2/incidents
  • POST/api/v2/incidents
  • GET/api/v2/incidents/:id
  • PATCH/api/v2/incidents/:id

logs 1

  • POST/api/v2/logs/events/search

monitor 6

  • GET/api/v1/monitor
  • GET/api/v1/monitor/:id
  • POST/api/v1/monitor/:id/mute
  • POST/api/v1/monitor/:id/unmute
  • GET/api/v1/monitor/:monitor_id/downtimes
  • GET/api/v2/monitor/:monitor_id/downtime_matches

query 1

  • GET/api/v1/query
PagerDutyIncidents, on-call and escalation Ready17 endpoints
API
REST v2 / Events v2 subset · HTTP
Resources
Incidents, Services, People, Schedules
Starter data
4 services · 4 people · 5 incidents
Your agent gets
PAGERDUTY_API_URL PAGERDUTY_API_TOKEN PAGERDUTY_FROM_EMAIL PAGERDUTY_ROUTING_KEY PAGERDUTY_ROUTING_KEYS PAGERDUTY_SIGNING_SECRET
Tested with
@pagerduty/pdjs 2.2.4
Limits
Finite explicit schedules and escalations.

Endpoints 17

PagerDuty in the docs →

enqueue 1

  • POST/v2/enqueue

escalation_policies 2

  • GET/escalation_policies
  • GET/escalation_policies/:id

incidents 6

  • GET/incidents
  • GET/incidents/:id
  • PUT/incidents/:id
  • GET/incidents/:id/log_entries
  • GET/incidents/:id/notes
  • POST/incidents/:id/notes

oncalls 1

  • GET/oncalls

schedules 3

  • GET/schedules
  • GET/schedules/:id
  • GET/schedules/:id/users

services 2

  • GET/services
  • GET/services/:id

users 2

  • GET/users
  • GET/users/:id
Better StackUptime monitors, heartbeats, incidents and status pages Ready29 endpoints
API
Uptime API v2 / v3 subset · HTTP
Resources
Monitors, Heartbeats, Incidents, On-call, Status pages
Your agent gets
BETTER_STACK_API_URL BETTER_STACK_API_TOKEN
Limits
Nothing is probed: a monitor is down while it has an open incident, and heartbeats recover when pinged. No escalation policies, paging, telemetry (logs) or status page subscribers. No official SDK exists; tested against the documented REST shapes.

Endpoints 29

Better Stack in the docs →

heartbeat 2

  • GET/api/v1/heartbeat/{token}
  • POST/api/v1/heartbeat/{token}

heartbeats 5

  • GET/api/v2/heartbeats
  • POST/api/v2/heartbeats
  • GET/api/v2/heartbeats/{id}
  • PATCH/api/v2/heartbeats/{id}
  • DELETE/api/v2/heartbeats/{id}

incidents 6

  • GET/api/v3/incidents
  • POST/api/v3/incidents
  • GET/api/v3/incidents/{id}
  • DELETE/api/v3/incidents/{id}
  • POST/api/v3/incidents/{id}/acknowledge
  • POST/api/v3/incidents/{id}/resolve

monitors 7

  • GET/api/v2/monitors
  • POST/api/v2/monitors
  • GET/api/v2/monitors/{id}
  • PATCH/api/v2/monitors/{id}
  • DELETE/api/v2/monitors/{id}
  • GET/api/v2/monitors/{id}/response-times
  • GET/api/v2/monitors/{id}/sla

on-calls 2

  • GET/api/v2/on-calls
  • GET/api/v2/on-calls/{id}

status-pages 7

  • GET/api/v2/status-pages
  • GET/api/v2/status-pages/{id}
  • GET/api/v2/status-pages/{id}/resources
  • GET/api/v2/status-pages/{id}/status-reports
  • POST/api/v2/status-pages/{id}/status-reports
  • GET/api/v2/status-pages/{id}/status-reports/{report_id}
  • POST/api/v2/status-pages/{id}/status-reports/{report_id}/status-updates
SentryIssues, error events, triage and releases Ready32 endpoints
API
REST API /api/0 subset · HTTP
Resources
Organizations, Projects, Teams, Members, Issues, Events, Tags, Comments, Releases, Deploys, Events query
Your agent gets
SENTRY_API_URL SENTRY_AUTH_TOKEN
Limits
Call ${SENTRY_API_URL}/api/0/... with Authorization: Bearer SENTRY_AUTH_TOKEN, using the shapes in Sentry’s API docs (Sentry’s generated API client is source-available, so the tests use HTTP). Lists page through the Link header (rel="next", results="true", cursor). Issue search covers Sentry’s syntax for status, assignment, level, priority, releases, environments, times, users, error fields and tags; the organization default is is:unresolved issue.priority:[high, medium] over 14 days. Client keys point their DSNs at this replica, but event ingestion is a gap, as are merging and discarding issues, release commits, alerts, and datasets other than errors in the events query.

Endpoints 32

Sentry in the docs →

0 32

  • GET/api/0/
  • GET/api/0/organizations/
  • GET/api/0/organizations/:org/
  • GET/api/0/organizations/:org/eventids/:event/
  • GET/api/0/organizations/:org/events/
  • GET/api/0/organizations/:org/issues/
  • PUT/api/0/organizations/:org/issues/
  • GET/api/0/organizations/:org/issues/:issue/
  • PUT/api/0/organizations/:org/issues/:issue/
  • DELETE/api/0/organizations/:org/issues/:issue/
  • GET/api/0/organizations/:org/issues/:issue/comments/
  • POST/api/0/organizations/:org/issues/:issue/comments/
  • GET/api/0/organizations/:org/issues/:issue/events/
  • GET/api/0/organizations/:org/issues/:issue/events/:event/
  • GET/api/0/organizations/:org/issues/:issue/tags/:key/
  • GET/api/0/organizations/:org/issues/:issue/tags/:key/values/
  • GET/api/0/organizations/:org/members/
  • GET/api/0/organizations/:org/projects/
  • GET/api/0/organizations/:org/releases/
  • POST/api/0/organizations/:org/releases/
  • GET/api/0/organizations/:org/releases/:version/
  • PUT/api/0/organizations/:org/releases/:version/
  • GET/api/0/organizations/:org/releases/:version/deploys/
  • POST/api/0/organizations/:org/releases/:version/deploys/
  • GET/api/0/organizations/:org/shortids/:short/
  • GET/api/0/organizations/:org/teams/
  • GET/api/0/projects/:org/:project/
  • GET/api/0/projects/:org/:project/events/
  • GET/api/0/projects/:org/:project/events/:event/
  • GET/api/0/projects/:org/:project/issues/
  • GET/api/0/projects/:org/:project/keys/
  • GET/api/0/projects/:org/:project/releases/

Customer support 2

ZendeskSupport tickets, replies, people and organizations Ready21 endpoints
API
Support API v2 subset · HTTP
Resources
Tickets, Comments, Search, Users, Organizations, Groups, Macros, Views
Your agent gets
ZENDESK_API_URL ZENDESK_EMAIL ZENDESK_API_TOKEN
Limits
Send ZENDESK_EMAIL/token:ZENDESK_API_TOKEN as Basic auth to ZENDESK_API_URL (it ends in /api/v2; paths take an optional .json). Zendesk publishes no official Node client; the tests use the documented HTTP shapes. Replies are recorded, never emailed; no triggers, automations, SLAs, custom fields, attachments or Help Center. Search covers the common ticket, user and organization properties; other properties are reported as gaps.

Endpoints 21

Zendesk in the docs →

groups 1

  • GET/api/v2/groups

macros 1

  • GET/api/v2/macros

organizations 3

  • GET/api/v2/organizations
  • GET/api/v2/organizations/{id}
  • GET/api/v2/organizations/{id}/tickets

search 1

  • GET/api/v2/search

tickets 7

  • GET/api/v2/tickets
  • POST/api/v2/tickets
  • GET/api/v2/tickets/{id}
  • PUT/api/v2/tickets/{id}
  • DELETE/api/v2/tickets/{id}
  • GET/api/v2/tickets/{id}/comments
  • GET/api/v2/tickets/{id}/macros/{macro_id}/apply

users 6

  • GET/api/v2/users
  • POST/api/v2/users
  • GET/api/v2/users/{id}
  • GET/api/v2/users/{id}/tickets/requested
  • GET/api/v2/users/me
  • GET/api/v2/users/search

views 2

  • GET/api/v2/views
  • GET/api/v2/views/{id}/tickets
IntercomInbox conversations, contacts, companies, tags, notes and help center articles Ready48 endpoints
API
API 2.14 subset · HTTP
Resources
Conversations, Contacts, Companies, Tags, Notes, Admins, Teams, Articles
Your agent gets
INTERCOM_API_URL INTERCOM_ACCESS_TOKEN
Tested with
intercom-client 7.0.3
Limits
Point the official intercom-client at INTERCOM_API_URL with its baseUrl option. Gaps answer 400 in Intercom’s error shape (marked as gaps), since the client retries every 5xx. Tickets, outbound messages, data events, segments, subscriptions and AI agent fields are gaps.

Endpoints 48

Intercom in the docs →

admins 3

  • GET/admins
  • GET/admins/:id
  • PUT/admins/:id/away

articles 5

  • GET/articles
  • POST/articles
  • GET/articles/:id
  • PUT/articles/:id
  • GET/articles/search

companies 6

  • GET/companies
  • POST/companies
  • GET/companies/:id
  • PUT/companies/:id
  • GET/companies/:id/contacts
  • POST/companies/list

contacts 17

  • GET/contacts
  • POST/contacts
  • GET/contacts/:id
  • PUT/contacts/:id
  • DELETE/contacts/:id
  • POST/contacts/:id/archive
  • GET/contacts/:id/companies
  • POST/contacts/:id/companies
  • DELETE/contacts/:id/companies/:company
  • GET/contacts/:id/notes
  • POST/contacts/:id/notes
  • GET/contacts/:id/tags
  • POST/contacts/:id/tags
  • DELETE/contacts/:id/tags/:tag
  • POST/contacts/:id/unarchive
  • GET/contacts/find_by_external_id/:id
  • POST/contacts/search

conversations 9

  • GET/conversations
  • POST/conversations
  • GET/conversations/:id
  • PUT/conversations/:id
  • POST/conversations/:id/parts
  • POST/conversations/:id/reply
  • POST/conversations/:id/tags
  • DELETE/conversations/:id/tags/:tag
  • POST/conversations/search

me 1

  • GET/me

notes 1

  • GET/notes/:id

tags 4

  • GET/tags
  • POST/tags
  • GET/tags/:id
  • DELETE/tags/:id

teams 2

  • GET/teams
  • GET/teams/:id

Payments and commerce 3

StripeCustomers, subscriptions, invoices and payments Ready34 endpoints
API
API 2026-10-28.endive subset · HTTP
Resources
Customers, Products, Prices, Subscriptions, Invoices, Invoice items, Payment intents, Charges, Refunds, Balance
Your agent gets
STRIPE_API_URL STRIPE_API_HOST_URL STRIPE_SECRET_KEY
Tested with
stripe 23.1.0
Limits
Test mode only: cards are test tokens (pm_card_visa, pm_card_chargeDeclined…) or seeded cards; no 3D Secure, payouts, disputes, taxes, coupons or webhooks. The SDK takes no base path: point host/port/protocol at the env-scoped host ({env}-stripe.localhost) or prefix STRIPE_API_URL in a custom fetch client. Requests pinned to an API version before 2025-03-31 are coverage gaps: older object shapes are not served.

Endpoints 34

Stripe in the docs →

balance 1

  • GET/v1/balance

charges 2

  • GET/v1/charges
  • GET/v1/charges/:id

customers 6

  • GET/v1/customers
  • POST/v1/customers
  • GET/v1/customers/:id
  • POST/v1/customers/:id
  • DELETE/v1/customers/:id
  • GET/v1/customers/search

invoiceitems 2

  • GET/v1/invoiceitems
  • POST/v1/invoiceitems

invoices 7

  • GET/v1/invoices
  • POST/v1/invoices
  • GET/v1/invoices/:id
  • POST/v1/invoices/:id
  • POST/v1/invoices/:id/finalize
  • POST/v1/invoices/:id/pay
  • POST/v1/invoices/:id/void

payment_intents 5

  • GET/v1/payment_intents
  • POST/v1/payment_intents
  • GET/v1/payment_intents/:id
  • POST/v1/payment_intents/:id/cancel
  • POST/v1/payment_intents/:id/confirm

prices 2

  • GET/v1/prices
  • GET/v1/prices/:id

products 2

  • GET/v1/products
  • GET/v1/products/:id

refunds 3

  • GET/v1/refunds
  • POST/v1/refunds
  • GET/v1/refunds/:id

subscriptions 4

  • GET/v1/subscriptions
  • GET/v1/subscriptions/:id
  • POST/v1/subscriptions/:id
  • DELETE/v1/subscriptions/:id
PayPalCheckout orders, payments, refunds, subscriptions and transaction reports Ready35 endpoints
API
REST subset · HTTP
Resources
Orders, Authorizations, Captures, Refunds, Plans, Subscriptions, Transactions, Balances
Your agent gets
PAYPAL_API_URL PAYPAL_CLIENT_ID PAYPAL_CLIENT_SECRET
Tested with
@paypal/paypal-server-sdk 2.5.0
Limits
Exchange PAYPAL_CLIENT_ID and PAYPAL_CLIENT_SECRET at ${PAYPAL_API_URL}/v1/oauth2/token. The server SDK only knows PayPal’s own hosts: call PAYPAL_API_URL over HTTP, or give the SDK an axios adapter (unstable_httpClientOptions) that swaps https://api-m.sandbox.paypal.com for it. Payers approve orders and subscriptions in their browser, which the twin cannot do: new ones wait for approval, seeded approved orders can be captured. Invoicing, disputes, payouts and webhooks are gaps.

Endpoints 35

PayPal in the docs →

billing 15

  • GET/v1/billing/plans
  • POST/v1/billing/plans
  • GET/v1/billing/plans/:id
  • POST/v1/billing/plans/:id/activate
  • POST/v1/billing/plans/:id/deactivate
  • GET/v1/billing/subscriptions
  • POST/v1/billing/subscriptions
  • GET/v1/billing/subscriptions/:id
  • PATCH/v1/billing/subscriptions/:id
  • POST/v1/billing/subscriptions/:id/activate
  • POST/v1/billing/subscriptions/:id/cancel
  • POST/v1/billing/subscriptions/:id/capture
  • POST/v1/billing/subscriptions/:id/revise
  • POST/v1/billing/subscriptions/:id/suspend
  • GET/v1/billing/subscriptions/:id/transactions

catalogs 2

  • GET/v1/catalogs/products
  • GET/v1/catalogs/products/:id

checkout 8

  • POST/v2/checkout/orders
  • GET/v2/checkout/orders/:id
  • PATCH/v2/checkout/orders/:id
  • POST/v2/checkout/orders/:id/authorize
  • POST/v2/checkout/orders/:id/capture
  • POST/v2/checkout/orders/:id/confirm-payment-source
  • POST/v2/checkout/orders/:id/track
  • PATCH/v2/checkout/orders/:id/trackers/:tracker

oauth2 1

  • POST/v1/oauth2/token

payments 7

  • GET/v2/payments/authorizations/:id
  • POST/v2/payments/authorizations/:id/capture
  • POST/v2/payments/authorizations/:id/reauthorize
  • POST/v2/payments/authorizations/:id/void
  • GET/v2/payments/captures/:id
  • POST/v2/payments/captures/:id/refund
  • GET/v2/payments/refunds/:id

reporting 2

  • GET/v1/reporting/balances
  • GET/v1/reporting/transactions
ShopifyOrders, products, inventory, customers, fulfillments and refunds Ready32 endpoints
API
Admin GraphQL 2026-10 subset · HTTP
Resources
Orders, Products, Inventory, Customers, Fulfillments, Refunds, Locations
Your agent gets
SHOPIFY_API_URL SHOPIFY_ACCESS_TOKEN SHOPIFY_API_VERSION
Tested with
@shopify/admin-api-client 2.0.1
Limits
The endpoint is ${SHOPIFY_API_URL}/admin/api/2026-10/graphql.json with the X-Shopify-Access-Token header. @shopify/admin-api-client always calls https://<store>.myshopify.com: give it a customFetchApi that swaps that origin for SHOPIFY_API_URL. The REST Admin API, webhooks, discounts, draft orders, returns and metafields are gaps; query cost is an estimate of Shopify’s.

Endpoints 32

Shopify in the docs →

customer 1

  • QUERYcustomer

customerCreate 1

  • MUTATIONcustomerCreate

customers 1

  • QUERYcustomers

customerUpdate 1

  • MUTATIONcustomerUpdate

fulfillmentCreate 1

  • MUTATIONfulfillmentCreate

fulfillmentOrder 1

  • QUERYfulfillmentOrder

fulfillmentTrackingInfoUpdate 1

  • MUTATIONfulfillmentTrackingInfoUpdate

inventoryAdjustQuantities 1

  • MUTATIONinventoryAdjustQuantities

inventoryItem 1

  • QUERYinventoryItem

inventorySetQuantities 1

  • MUTATIONinventorySetQuantities

job 1

  • QUERYjob

location 1

  • QUERYlocation

locations 1

  • QUERYlocations

node 1

  • QUERYnode

nodes 1

  • QUERYnodes

order 1

  • QUERYorder

orderCancel 1

  • MUTATIONorderCancel

orderClose 1

  • MUTATIONorderClose

orderMarkAsPaid 1

  • MUTATIONorderMarkAsPaid

orderOpen 1

  • MUTATIONorderOpen

orders 1

  • QUERYorders

orderUpdate 1

  • MUTATIONorderUpdate

product 1

  • QUERYproduct

products 1

  • QUERYproducts

productUpdate 1

  • MUTATIONproductUpdate

productVariant 1

  • QUERYproductVariant

productVariants 1

  • QUERYproductVariants

productVariantsBulkUpdate 1

  • MUTATIONproductVariantsBulkUpdate

refundCreate 1

  • MUTATIONrefundCreate

shop 1

  • QUERYshop

tagsAdd 1

  • MUTATIONtagsAdd

tagsRemove 1

  • MUTATIONtagsRemove

CRM and sales 4

SalesforceAccounts, contacts and pipeline Ready14 endpoints
API
REST v67.0 · HTTP
Resources
Accounts, Contacts, Leads, Opportunities, Campaigns
Starter data
7 accounts · 6 contacts · 4 leads · 6 opportunities
Your agent gets
SALESFORCE_INSTANCE_URL SALESFORCE_ACCESS_TOKEN
Limits
Bounded SOQL and standard object fields; no Apex or arbitrary automation.

Endpoints 14

Salesforce in the docs →

composite 1

  • POST/services/data/v67.0/composite

query 2

  • GET/services/data/v67.0/query
  • GET/services/data/v67.0/query/:locator

sobjects 9

  • GET/services/data/v67.0/sobjects
  • GET/services/data/v67.0/sobjects/:type
  • POST/services/data/v67.0/sobjects/:type
  • GET/services/data/v67.0/sobjects/:type/:field/:value
  • PATCH/services/data/v67.0/sobjects/:type/:field/:value
  • GET/services/data/v67.0/sobjects/:type/:id
  • PATCH/services/data/v67.0/sobjects/:type/:id
  • DELETE/services/data/v67.0/sobjects/:type/:id
  • GET/services/data/v67.0/sobjects/:type/describe

versions 2

  • GET/services/data/
  • GET/services/data/v67.0
HubSpotCompanies, contacts and deals Ready18 endpoints
API
CRM v3 · HTTP
Resources
Companies, Contacts, Deals, Pipelines
Starter data
9 companies · 13 contacts · 8 deals
Your agent gets
HUBSPOT_API_URL HUBSPOT_ACCESS_TOKEN
Limits
Selected CRM objects and search; delayed search indexing; no workflows.

Endpoints 18

HubSpot in the docs →

associations 2

  • POST/crm/v3/associations/:from/:to/batch/:operation
  • GET/crm/v3/associations/:from/:to/types

objects 10

  • GET/crm/v3/objects/:type
  • POST/crm/v3/objects/:type
  • GET/crm/v3/objects/:type/:id
  • PATCH/crm/v3/objects/:type/:id
  • DELETE/crm/v3/objects/:type/:id
  • GET/crm/v3/objects/:type/:id/associations/:to
  • PUT/crm/v3/objects/:type/:id/associations/:to/:toId/:associationType
  • DELETE/crm/v3/objects/:type/:id/associations/:to/:toId/:associationType
  • POST/crm/v3/objects/:type/batch/:operation
  • POST/crm/v3/objects/:type/search

pipelines 4

  • GET/crm/v3/pipelines/:type
  • GET/crm/v3/pipelines/:type/:id
  • GET/crm/v3/pipelines/:type/:id/stages
  • GET/crm/v3/pipelines/:type/:id/stages/:stage

properties 2

  • GET/crm/v3/properties/:type
  • GET/crm/v3/properties/:type/:property
AttioPeople, companies, deals, lists, notes and tasks Ready30 endpoints
API
REST v2 subset · HTTP
Resources
Objects, Attributes, Records, Lists, Entries, Notes, Tasks, Workspace members
Your agent gets
ATTIO_API_URL ATTIO_API_KEY
Limits
Standard people, companies and deals objects with typed values and value history; custom objects, webhooks, threads, comments and path filters are gaps. Attio publishes no official API client: tested over HTTP against the shapes in its OpenAPI document.

Endpoints 30

Attio in the docs →

attributes 1

  • GET/v2/:target/:identifier/attributes

lists 6

  • GET/v2/lists
  • GET/v2/lists/:list
  • POST/v2/lists/:list/entries
  • PATCH/v2/lists/:list/entries/:entry_id
  • DELETE/v2/lists/:list/entries/:entry_id
  • POST/v2/lists/:list/entries/query

notes 4

  • GET/v2/notes
  • POST/v2/notes
  • GET/v2/notes/:note_id
  • DELETE/v2/notes/:note_id

objects 11

  • GET/v2/objects
  • GET/v2/objects/:object
  • POST/v2/objects/:object/records
  • PUT/v2/objects/:object/records
  • GET/v2/objects/:object/records/:record_id
  • PUT/v2/objects/:object/records/:record_id
  • PATCH/v2/objects/:object/records/:record_id
  • DELETE/v2/objects/:object/records/:record_id
  • GET/v2/objects/:object/records/:record_id/attributes/:attribute/values
  • GET/v2/objects/:object/records/:record_id/entries
  • POST/v2/objects/:object/records/query

self 1

  • GET/v2/self

tasks 5

  • GET/v2/tasks
  • POST/v2/tasks
  • GET/v2/tasks/:task_id
  • PATCH/v2/tasks/:task_id
  • DELETE/v2/tasks/:task_id

workspace_members 2

  • GET/v2/workspace_members
  • GET/v2/workspace_members/:id
GongSales calls and customer conversations Ready5 endpoints
API
v2 subset · HTTP
Resources
Calls, Transcripts, People
Starter data
3 people · 8 calls
Your agent gets
GONG_API_URL GONG_ACCESS_KEY GONG_ACCESS_KEY_SECRET
Limits
Read-only call and transcript subset; no speech recognition or audio generation.

Endpoints 5

Gong in the docs →

calls 3

  • GET/v2/calls
  • POST/v2/calls/extensive
  • POST/v2/calls/transcript

users 1

  • GET/v2/users

workspaces 1

  • GET/v2/workspaces

Docs and files 6

NotionPages, databases, blocks and comments Ready19 endpoints
API
Notion-Version 2025-09-03 subset · HTTP
Resources
Pages, Blocks, Databases, Data sources, Comments, Users, Search
Your agent gets
NOTION_API_URL NOTION_TOKEN
Tested with
@notionhq/client 5.30.0
Limits
An internal integration: it sees only pages shared with it, as Notion does. Text, heading, list, to-do, toggle, quote, callout, code, divider and bookmark blocks; images, files, tables, synced blocks, relations, rollups, formulas and markdown endpoints are gaps. Requests with a Notion-Version before 2025-09-03 are coverage gaps: databases are served as data sources.

Endpoints 19

Notion in the docs →

blocks 5

  • GET/v1/blocks/:block_id
  • PATCH/v1/blocks/:block_id
  • DELETE/v1/blocks/:block_id
  • GET/v1/blocks/:block_id/children
  • PATCH/v1/blocks/:block_id/children

comments 3

  • GET/v1/comments
  • POST/v1/comments
  • GET/v1/comments/:comment_id

data_sources 2

  • GET/v1/data_sources/:data_source_id
  • POST/v1/data_sources/:data_source_id/query

databases 1

  • GET/v1/databases/:database_id

pages 4

  • POST/v1/pages
  • GET/v1/pages/:page_id
  • PATCH/v1/pages/:page_id
  • GET/v1/pages/:page_id/properties/:property_id

search 1

  • POST/v1/search

users 3

  • GET/v1/users
  • GET/v1/users/:user_id
  • GET/v1/users/me
Google DriveFiles, folders, sharing and comments Ready26 endpoints
API
Drive API v3 subset · HTTP
Resources
Files, Folders, Permissions, Comments, Revisions, Changes
Your agent gets
GOOGLE_DRIVE_API_URL GOOGLE_DRIVE_ACCESS_TOKEN
Tested with
@googleapis/drive 26.0.2
Limits
My Drive for one signed-in account; no shared drives, push notifications or resumable uploads. Exports Docs, Sheets and Slides as text, Markdown, HTML, CSV or TSV; PDF and Office exports are coverage gaps. Sharing notifications are recorded in state, never emailed.

Endpoints 26

Google Drive in the docs →

drive 24

  • GET/drive/v3/about
  • GET/drive/v3/changes
  • GET/drive/v3/changes/startPageToken
  • GET/drive/v3/files
  • POST/drive/v3/files
  • GET/drive/v3/files/{fileId}
  • PATCH/drive/v3/files/{fileId}
  • DELETE/drive/v3/files/{fileId}
  • GET/drive/v3/files/{fileId}/comments
  • POST/drive/v3/files/{fileId}/comments
  • GET/drive/v3/files/{fileId}/comments/{commentId}
  • PATCH/drive/v3/files/{fileId}/comments/{commentId}
  • DELETE/drive/v3/files/{fileId}/comments/{commentId}
  • GET/drive/v3/files/{fileId}/comments/{commentId}/replies
  • POST/drive/v3/files/{fileId}/comments/{commentId}/replies
  • POST/drive/v3/files/{fileId}/copy
  • GET/drive/v3/files/{fileId}/export
  • GET/drive/v3/files/{fileId}/permissions
  • POST/drive/v3/files/{fileId}/permissions
  • GET/drive/v3/files/{fileId}/permissions/{permissionId}
  • PATCH/drive/v3/files/{fileId}/permissions/{permissionId}
  • DELETE/drive/v3/files/{fileId}/permissions/{permissionId}
  • GET/drive/v3/files/{fileId}/revisions
  • DELETE/drive/v3/files/trash

upload 2

  • POST/upload/drive/v3/files
  • PATCH/upload/drive/v3/files/{fileId}
DropboxFiles, folders, shared links and shared folders Ready24 endpoints
API
API v2 subset · HTTP
Resources
Files, Folders, Revisions, Shared links, Shared folders
Your agent gets
DROPBOX_API_URL DROPBOX_ACCESS_TOKEN
Tested with
dropbox 10.47.0
Limits
The SDK has no base-URL option: give it a fetch that sends https://api.dropboxapi.com and https://content.dropboxapi.com to DROPBOX_API_URL. One account; uploads up to 150 MB (no upload sessions), no file requests, Paper or team-space admin. Sharing records links and members; nothing is emailed.

Endpoints 24

Dropbox in the docs →

2 23

  • POST/2/files/copy_v2
  • POST/2/files/create_folder_v2
  • POST/2/files/delete_v2
  • POST/2/files/download
  • POST/2/files/get_metadata
  • POST/2/files/get_temporary_link
  • POST/2/files/list_folder
  • POST/2/files/list_folder/continue
  • POST/2/files/list_revisions
  • POST/2/files/move_v2
  • POST/2/files/restore
  • POST/2/files/search_v2
  • POST/2/files/search/continue_v2
  • POST/2/files/upload
  • POST/2/sharing/add_folder_member
  • POST/2/sharing/create_shared_link_with_settings
  • POST/2/sharing/list_folder_members
  • POST/2/sharing/list_shared_links
  • POST/2/sharing/modify_shared_link_settings
  • POST/2/sharing/revoke_shared_link
  • POST/2/sharing/share_folder
  • POST/2/users/get_current_account
  • POST/2/users/get_space_usage

temporary 1

  • GET/temporary/{token}
Amazon S3Buckets, objects and multipart uploads Ready25 endpoints
API
REST (SigV4) subset · HTTP
Resources
Buckets, Objects, Tags, Multipart uploads
Your agent gets
AWS_ENDPOINT_URL_S3 AWS_ACCESS_KEY_ID AWS_SECRET_ACCESS_KEY AWS_REGION
Tested with
@aws-sdk/client-s3 3.1152.0
Limits
Path-style addressing: the SDK chooses it for an IP endpoint; set forcePathStyle for a host name. One account and access key; per-bucket read-write, read-only or no access stands in for IAM policies. No versioning, object lock, ACLs, KMS encryption, Glacier restores or event notifications; presigned URLs are verified but never expire.

Endpoints 25

Amazon S3 in the docs →

{Bucket} 17

  • HEAD/{Bucket}
  • GET/{Bucket}
  • PUT/{Bucket}
  • DELETE/{Bucket}
  • HEAD/{Bucket}/{Key+}
  • GET/{Bucket}/{Key+}
  • PUT/{Bucket}/{Key+}
  • DELETE/{Bucket}/{Key+}
  • PUT/{Bucket}/{Key+} (x-amz-copy-source)
  • PUT/{Bucket}/{Key+}?partNumber&uploadId
  • GET/{Bucket}/{Key+}?tagging
  • PUT/{Bucket}/{Key+}?tagging
  • DELETE/{Bucket}/{Key+}?tagging
  • GET/{Bucket}/{Key+}?uploadId
  • POST/{Bucket}/{Key+}?uploadId
  • DELETE/{Bucket}/{Key+}?uploadId
  • POST/{Bucket}/{Key+}?uploads

{Bucket}?delete 1

  • POST/{Bucket}?delete

{Bucket}?list-type=2 1

  • GET/{Bucket}?list-type=2

{Bucket}?location 1

  • GET/{Bucket}?location

{Bucket}?tagging 3

  • GET/{Bucket}?tagging
  • PUT/{Bucket}?tagging
  • DELETE/{Bucket}?tagging

{Bucket}?uploads 1

  • GET/{Bucket}?uploads

versions 1

  • GET/
Microsoft WordWord documents in OneDrive through Microsoft Graph Ready21 endpoints
API
Graph v1.0 drive items · HTTP
Resources
Documents, Folders, Versions, Sharing links, Invitations
Your agent gets
MICROSOFT_GRAPH_API_URL MICROSOFT_GRAPH_ACCESS_TOKEN
Limits
One OneDrive; Word files are real .docx packages built from paragraphs, with PDF conversion. No Word document object model, comments or co-authoring. The Graph client signs only https Graph hosts and deletes an Authorization header sent elsewhere: set baseUrl to MICROSOFT_GRAPH_API_URL plus / and pass the token as a lower-case authorization header in fetchOptions.headers. Its api() only takes https URLs: follow @odata.nextLink with the part after /v1.0. Invitations and sharing are recorded, never emailed; no upload sessions, delta or shared-with-me.

Endpoints 21

Microsoft Word in the docs →

download 1

  • GET/download/{token}

monitor 1

  • GET/monitor/{token}

v1 19

  • GET/v1.0/me
  • GET/v1.0/me/drive
  • GET/v1.0/me/drive/items/{item-id}
  • PATCH/v1.0/me/drive/items/{item-id}
  • DELETE/v1.0/me/drive/items/{item-id}
  • GET/v1.0/me/drive/items/{item-id}/children
  • POST/v1.0/me/drive/items/{item-id}/children
  • GET/v1.0/me/drive/items/{item-id}/content
  • POST/v1.0/me/drive/items/{item-id}/copy
  • POST/v1.0/me/drive/items/{item-id}/createLink
  • POST/v1.0/me/drive/items/{item-id}/invite
  • GET/v1.0/me/drive/items/{item-id}/permissions
  • DELETE/v1.0/me/drive/items/{item-id}/permissions/{perm-id}
  • GET/v1.0/me/drive/items/{item-id}/versions
  • GET/v1.0/me/drive/items/{item-id}/versions/{version-id}/content
  • POST/v1.0/me/drive/items/{item-id}/versions/{version-id}/restoreVersion
  • PUT/v1.0/me/drive/items/{parent-id}:/{filename}:/content
  • GET/v1.0/me/drive/recent
  • GET/v1.0/me/drive/root/search(q='{text}')
AirtableBases of linked tables: records, views, formulas and comments Ready21 endpoints
API
Web API v0 subset · HTTP
Resources
Bases, Tables, Fields, Records, Views, Formulas, Comments
Your agent gets
AIRTABLE_API_URL AIRTABLE_ENDPOINT_URL AIRTABLE_API_KEY
Limits
Send AIRTABLE_API_KEY (a personal access token) as a Bearer token to AIRTABLE_API_URL (it ends in /v0). The official airtable.js client reads AIRTABLE_API_KEY and AIRTABLE_ENDPOINT_URL by itself; these tests use the documented HTTP API. filterByFormula, view filters and formula, count, lookup and rollup fields run on a formula engine with most of Airtable’s functions (the rest are reported as gaps); links stay in step on both sides; TODAY() and NOW() follow the scene clock. No attachments, webhooks, sync tables, cellFormat=string or new bases.

Endpoints 21

Airtable in the docs →

{baseId} 14

  • GET/v0/{baseId}/{tableIdOrName}
  • POST/v0/{baseId}/{tableIdOrName}
  • PUT/v0/{baseId}/{tableIdOrName}
  • PATCH/v0/{baseId}/{tableIdOrName}
  • DELETE/v0/{baseId}/{tableIdOrName}
  • GET/v0/{baseId}/{tableIdOrName}/{recordId}
  • PUT/v0/{baseId}/{tableIdOrName}/{recordId}
  • PATCH/v0/{baseId}/{tableIdOrName}/{recordId}
  • DELETE/v0/{baseId}/{tableIdOrName}/{recordId}
  • GET/v0/{baseId}/{tableIdOrName}/{recordId}/comments
  • POST/v0/{baseId}/{tableIdOrName}/{recordId}/comments
  • PATCH/v0/{baseId}/{tableIdOrName}/{recordId}/comments/{rowCommentId}
  • DELETE/v0/{baseId}/{tableIdOrName}/{recordId}/comments/{rowCommentId}
  • POST/v0/{baseId}/{tableIdOrName}/listRecords

meta 7

  • GET/v0/meta/bases
  • GET/v0/meta/bases/{baseId}/tables
  • POST/v0/meta/bases/{baseId}/tables
  • POST/v0/meta/bases/{baseId}/tables/{tableId}/fields
  • PATCH/v0/meta/bases/{baseId}/tables/{tableId}/fields/{columnId}
  • PATCH/v0/meta/bases/{baseId}/tables/{tableIdOrName}
  • GET/v0/meta/whoami

Identity 2

OktaPeople, groups, app assignments and the System Log Ready31 endpoints
API
Management API v1 subset · HTTP
Resources
Users, Groups, Applications, App assignments, System Log
Your agent gets
OKTA_ORG_URL OKTA_API_TOKEN
Tested with
@okta/okta-sdk-nodejs 8.2.0
Limits
One org and one SSWS API token owned by a super administrator; no OAuth service apps, factors, policies or sign-in flows. Lifecycle changes are immediate; activation and reset links are returned, never emailed. The System Log records every change made through the API; it gives no polling next link.

Endpoints 31

Okta in the docs →

apps 8

  • GET/api/v1/apps
  • GET/api/v1/apps/{appId}
  • GET/api/v1/apps/{appId}/groups
  • PUT/api/v1/apps/{appId}/groups/{groupId}
  • DELETE/api/v1/apps/{appId}/groups/{groupId}
  • GET/api/v1/apps/{appId}/users
  • POST/api/v1/apps/{appId}/users
  • DELETE/api/v1/apps/{appId}/users/{userId}

groups 8

  • GET/api/v1/groups
  • POST/api/v1/groups
  • GET/api/v1/groups/{groupId}
  • PUT/api/v1/groups/{groupId}
  • DELETE/api/v1/groups/{groupId}
  • GET/api/v1/groups/{groupId}/users
  • PUT/api/v1/groups/{groupId}/users/{userId}
  • DELETE/api/v1/groups/{groupId}/users/{userId}

logs 1

  • GET/api/v1/logs

users 14

  • GET/api/v1/users
  • POST/api/v1/users
  • GET/api/v1/users/{id}
  • POST/api/v1/users/{id}
  • DELETE/api/v1/users/{id}
  • GET/api/v1/users/{id}/appLinks
  • GET/api/v1/users/{id}/groups
  • POST/api/v1/users/{id}/lifecycle/activate
  • POST/api/v1/users/{id}/lifecycle/deactivate
  • POST/api/v1/users/{id}/lifecycle/reset_password
  • POST/api/v1/users/{id}/lifecycle/suspend
  • POST/api/v1/users/{id}/lifecycle/unlock
  • POST/api/v1/users/{id}/lifecycle/unsuspend
  • DELETE/api/v1/users/{id}/sessions
ClerkUsers, organizations, invitations and sessions Ready32 endpoints
API
Backend API v1 subset · HTTP
Resources
Users, Organizations, Memberships, Invitations, Sessions
Your agent gets
CLERK_API_URL CLERK_SECRET_KEY
Limits
One application instance with email sign-in; phone numbers, web3 wallets, SAML and imported password hashes are coverage gaps. Invitations are recorded, never emailed; pending ones expire on the scene clock. Session tokens and JWT verification are not modeled; sessions can be listed and revoked.

Endpoints 32

Clerk in the docs →

invitations 3

  • GET/v1/invitations
  • POST/v1/invitations
  • POST/v1/invitations/{invitation_id}/revoke

organizations 14

  • GET/v1/organizations
  • POST/v1/organizations
  • GET/v1/organizations/{organization_id}
  • PATCH/v1/organizations/{organization_id}
  • DELETE/v1/organizations/{organization_id}
  • GET/v1/organizations/{organization_id}/invitations
  • POST/v1/organizations/{organization_id}/invitations
  • GET/v1/organizations/{organization_id}/invitations/{invitation_id}
  • POST/v1/organizations/{organization_id}/invitations/{invitation_id}/revoke
  • GET/v1/organizations/{organization_id}/memberships
  • POST/v1/organizations/{organization_id}/memberships
  • PATCH/v1/organizations/{organization_id}/memberships/{user_id}
  • DELETE/v1/organizations/{organization_id}/memberships/{user_id}
  • PATCH/v1/organizations/{organization_id}/metadata

sessions 3

  • GET/v1/sessions
  • GET/v1/sessions/{session_id}
  • POST/v1/sessions/{session_id}/revoke

users 12

  • GET/v1/users
  • POST/v1/users
  • GET/v1/users/{user_id}
  • PATCH/v1/users/{user_id}
  • DELETE/v1/users/{user_id}
  • POST/v1/users/{user_id}/ban
  • POST/v1/users/{user_id}/lock
  • PATCH/v1/users/{user_id}/metadata
  • GET/v1/users/{user_id}/organization_memberships
  • POST/v1/users/{user_id}/unban
  • POST/v1/users/{user_id}/unlock
  • GET/v1/users/count

Marketing 4

Google Analytics 4Traffic, campaigns and conversions Ready4 endpoints
API
Data API v1beta REST · HTTP
Resources
Properties, Traffic, Campaign performance
Starter data
2 properties · 19 sessions
Your agent gets
GA4_API_URL GA4_ACCESS_TOKEN
Tested with
@googleapis/analyticsdata 10.1.1
Limits
Synthetic historical reports; selected dimensions and metrics; no live collection or attribution model.

Endpoints 4

Google Analytics 4 in the docs →

properties 4

  • POST/v1beta/properties/:property:batchRunReports
  • POST/v1beta/properties/:property:checkCompatibility
  • POST/v1beta/properties/:property:runReport
  • GET/v1beta/properties/:property/metadata
LinkedIn AdsCampaigns, audiences and performance Ready17 endpoints
API
202610 · HTTP
Resources
Ad accounts, Campaigns, Creatives, Performance
Starter data
2 campaigns · 2 creatives
Your agent gets
LINKEDIN_ADS_API_URL LINKEDIN_ADS_TOKEN
Limits
Selected single-image campaign operations; historical synthetic reports; no auction or real ad delivery.

Endpoints 17

LinkedIn Ads in the docs →

adAccounts 2

  • GET/rest/adAccounts
  • GET/rest/adAccounts/:accountId

adAnalytics 1

  • GET/rest/adAnalytics

adCampaignGroups 4

  • GET/rest/adAccounts/:accountId/adCampaignGroups
  • POST/rest/adAccounts/:accountId/adCampaignGroups
  • GET/rest/adAccounts/:accountId/adCampaignGroups/:id
  • POST/rest/adAccounts/:accountId/adCampaignGroups/:id

adCampaigns 4

  • GET/rest/adAccounts/:accountId/adCampaigns
  • POST/rest/adAccounts/:accountId/adCampaigns
  • GET/rest/adAccounts/:accountId/adCampaigns/:id
  • POST/rest/adAccounts/:accountId/adCampaigns/:id

adTargetingEntities 1

  • GET/rest/adTargetingEntities

adTargetingFacets 1

  • GET/rest/adTargetingFacets

creatives 4

  • GET/rest/adAccounts/:accountId/creatives
  • POST/rest/adAccounts/:accountId/creatives
  • GET/rest/adAccounts/:accountId/creatives/:id
  • POST/rest/adAccounts/:accountId/creatives/:id
ChatGPT AdsCampaigns, creative reviews and insights Ready26 endpoints
API
Advertiser API v1 · HTTP
Resources
Ad account, Campaigns, Ad groups, Ads, Insights
Starter data
2 campaigns · 2 ads · 2 insight rows
Your agent gets
OPENAI_ADS_API_URL OPENAI_ADS_API_KEY
Limits
Single-image chat cards and historical insights; local review model; no uploads, auction or conversion attribution.

Endpoints 26

ChatGPT Ads in the docs →

ad_account 2

  • GET/v1/ad_account
  • GET/v1/ad_account/insights

ad_groups 8

  • GET/v1/ad_groups
  • POST/v1/ad_groups
  • GET/v1/ad_groups/:id
  • POST/v1/ad_groups/:id
  • POST/v1/ad_groups/:id/activate
  • POST/v1/ad_groups/:id/archive
  • GET/v1/ad_groups/:id/insights
  • POST/v1/ad_groups/:id/pause

ads 8

  • GET/v1/ads
  • POST/v1/ads
  • GET/v1/ads/:id
  • POST/v1/ads/:id
  • POST/v1/ads/:id/activate
  • POST/v1/ads/:id/archive
  • GET/v1/ads/:id/insights
  • POST/v1/ads/:id/pause

campaigns 8

  • GET/v1/campaigns
  • POST/v1/campaigns
  • GET/v1/campaigns/:id
  • POST/v1/campaigns/:id
  • POST/v1/campaigns/:id/activate
  • POST/v1/campaigns/:id/archive
  • GET/v1/campaigns/:id/insights
  • POST/v1/campaigns/:id/pause

Other 4

LobLetters, postcards and checks by mail, with US address verification Ready28 endpoints
API
Print & Mail API v1 subset · HTTP
Resources
Addresses, Letters, Postcards, Checks, Bank accounts, Templates, US verifications
Your agent gets
LOB_API_URL LOB_API_KEY LOB_ASSETS_URL
Tested with
@lob/lob-typescript-sdk 1.4.2
Limits
Nothing is printed or mailed: USPS tracking follows the scene clock, and mail to an address the postal directory does not know, or a vacant one, comes back. Pass LOB_API_URL (it ends in /v1) as the SDK Configuration basePath and LOB_API_KEY as its username. Proof links name https://lob-assets.com as Lob’s do (the SDK rejects any other host); fetch them under LOB_ASSETS_URL instead. US verification consults the world’s postal directory. File URLs are recorded, never fetched; no thumbnails, self-mailers, campaigns, international verification or webhooks.

Endpoints 28

Lob in the docs →

addresses 4

  • GET/v1/addresses
  • POST/v1/addresses
  • GET/v1/addresses/{id}
  • DELETE/v1/addresses/{id}

bank_accounts 5

  • GET/v1/bank_accounts
  • POST/v1/bank_accounts
  • GET/v1/bank_accounts/{id}
  • DELETE/v1/bank_accounts/{id}
  • POST/v1/bank_accounts/{id}/verify

bulk 1

  • POST/v1/bulk/us_verifications

checks 4

  • GET/v1/checks
  • POST/v1/checks
  • GET/v1/checks/{id}
  • DELETE/v1/checks/{id}

letters 4

  • GET/v1/letters
  • POST/v1/letters
  • GET/v1/letters/{id}
  • DELETE/v1/letters/{id}

postcards 4

  • GET/v1/postcards
  • POST/v1/postcards
  • GET/v1/postcards/{id}
  • DELETE/v1/postcards/{id}

templates 5

  • GET/v1/templates
  • POST/v1/templates
  • GET/v1/templates/{id}
  • POST/v1/templates/{id}
  • DELETE/v1/templates/{id}

us_verifications 1

  • POST/v1/us_verifications
KalshiEvent contracts: markets, order books, orders, positions and settlements Ready25 endpoints
API
Trade API v2 subset · HTTP
Resources
Series, Events, Markets, Order books, Orders, Fills, Positions, Settlements
Your agent gets
KALSHI_API_URL KALSHI_API_KEY_ID KALSHI_PRIVATE_KEY
Tested with
kalshi-typescript 3.34.0
Limits
Pass KALSHI_API_URL (it ends in /trade-api/v2) as the SDK basePath, KALSHI_API_KEY_ID as apiKey and KALSHI_PRIVATE_KEY as privateKeyPem: requests are signed with RSA-PSS as on Kalshi; the timestamp’s age is not checked. Orders trade against other traders’ resting bids seeded with the scene, at the resting price, with Kalshi’s fee; nobody else trades unless the scene says so, and no money moves. Primary subaccount only. No order groups, RFQs or quotes, candlesticks, historical data, WebSockets or FIX.

Endpoints 25

Kalshi in the docs →

trade-api 25

  • GET/trade-api/v2/events
  • GET/trade-api/v2/events/{event_ticker}
  • GET/trade-api/v2/exchange/schedule
  • GET/trade-api/v2/exchange/status
  • GET/trade-api/v2/markets
  • GET/trade-api/v2/markets/{ticker}
  • GET/trade-api/v2/markets/{ticker}/orderbook
  • GET/trade-api/v2/markets/trades
  • GET/trade-api/v2/portfolio/balance
  • POST/trade-api/v2/portfolio/events/orders
  • DELETE/trade-api/v2/portfolio/events/orders
  • DELETE/trade-api/v2/portfolio/events/orders/{order_id}
  • POST/trade-api/v2/portfolio/events/orders/{order_id}/amend
  • POST/trade-api/v2/portfolio/events/orders/{order_id}/decrease
  • POST/trade-api/v2/portfolio/events/orders/batched
  • DELETE/trade-api/v2/portfolio/events/orders/batched
  • GET/trade-api/v2/portfolio/fills
  • GET/trade-api/v2/portfolio/orders
  • POST/trade-api/v2/portfolio/orders
  • GET/trade-api/v2/portfolio/orders/{order_id}
  • DELETE/trade-api/v2/portfolio/orders/{order_id}
  • GET/trade-api/v2/portfolio/positions
  • GET/trade-api/v2/portfolio/settlements
  • GET/trade-api/v2/series
  • GET/trade-api/v2/series/{series_ticker}
Open-MeteoWeather forecasts and place lookup Ready2 endpoints
API
v1 subset · HTTP
Resources
Places, Current conditions, Hourly, Daily
Starter data
10 places
Your agent gets
OPEN_METEO_API_URL OPEN_METEO_GEOCODING_URL
Limits
Synthetic climate per seeded place, moved by the scene clock; metric units; one location per request; no historical archive or marine/air-quality endpoints.

Endpoints 2

Open-Meteo in the docs →

forecast 1

  • GET/v1/forecast

search 1

  • GET/v1/search
Google CalendarCalendars, events, attendees, recurrence and free/busy Ready20 endpoints
API
API v3 subset · HTTP
Resources
Calendar list, Calendars, Events, Instances, Free/busy, Settings
Your agent gets
GOOGLE_CALENDAR_API_URL GOOGLE_CALENDAR_ACCESS_TOKEN
Tested with
@googleapis/calendar 20.1.0
Limits
Give the official client GOOGLE_CALENDAR_API_URL as the per-request rootUrl (a global rootUrl keeps only the origin). Gaps answer 400 in Google’s error shape (marked as gaps), since the client retries 5xx responses. Changing or deleting one occurrence of a recurring event, quickAdd, import, ACLs, watch channels and sync tokens are gaps.

Endpoints 20

Google Calendar in the docs →

calendar 20

  • POST/calendar/v3/calendars
  • GET/calendar/v3/calendars/:calendarId
  • PATCH/calendar/v3/calendars/:calendarId
  • DELETE/calendar/v3/calendars/:calendarId
  • GET/calendar/v3/calendars/:calendarId/events
  • POST/calendar/v3/calendars/:calendarId/events
  • GET/calendar/v3/calendars/:calendarId/events/:eventId
  • PUT/calendar/v3/calendars/:calendarId/events/:eventId
  • PATCH/calendar/v3/calendars/:calendarId/events/:eventId
  • DELETE/calendar/v3/calendars/:calendarId/events/:eventId
  • GET/calendar/v3/calendars/:calendarId/events/:eventId/instances
  • POST/calendar/v3/calendars/:calendarId/events/:eventId/move
  • POST/calendar/v3/calendars/:calendarId/events/import
  • POST/calendar/v3/calendars/:calendarId/events/quickAdd
  • GET/calendar/v3/colors
  • POST/calendar/v3/freeBusy
  • GET/calendar/v3/users/me/calendarList
  • GET/calendar/v3/users/me/calendarList/:calendarId
  • GET/calendar/v3/users/me/settings
  • GET/calendar/v3/users/me/settings/:setting

Missing a tool?

Tell us which one and what your agent does with it.