Configuration Examples
GitHub API
OpenAI API
Stripe API
SendGrid API
Twilio API
Twilio uses Basic authentication with your Account SID as username and Auth Token as password.
Authentication Patterns
Bearer Token (Most Common)
Used by most modern APIs:- GitHub
- OpenAI
- Stripe
- SendGrid
- Slack
Custom Header
Some APIs use custom header names:- Exa (x-api-key)
- Anthropic (x-api-key)
- AWS services (various)
Query Parameter
Legacy APIs often use query parameter auth:?key={your_api_key} to requests.
Basic Authentication
For APIs requiring username/password:Common Patterns
APIs with Versioned Base URLs
Include the version in the base URL:APIs with Tenant-Specific URLs
For multi-tenant APIs:Self-Hosted APIs
For internal or self-hosted services:Choosing a Test Endpoint
Select an endpoint that:- Requires authentication (validates credentials)
- Returns quickly (lightweight response)
- Is always available (not rate-limited)
| Pattern | Example | Notes |
|---|---|---|
| User/account info | /user, /me, /account | Validates auth, returns user data |
| Health check | /health, /ping, /status | May not require auth |
| List with limit | /items?limit=1 | Validates auth with minimal data |
Working with API Sources
Once configured, your agent can make requests to any endpoint under the base URL.Request Format
The agent uses the HTTP tool to make requests:Headers and Body
The agent can specify:- HTTP method (GET, POST, PUT, DELETE, PATCH)
- Path (relative to base URL)
- Query parameters
- Request body (JSON)
- Additional headers
Response Handling
API responses are processed intelligently:- JSON responses are parsed and presented clearly
- Large responses may be summarized
- Errors are reported with status codes and messages
- Rate limits are surfaced to help debug issues
Troubleshooting
Connection test fails
Connection test fails
- Verify the base URL is correct and accessible
- Check if the test endpoint exists and is spelled correctly
- Ensure credentials are valid and have necessary permissions
- Some APIs require specific headers - check documentation
Authentication not working
Authentication not working
- Confirm you are using the correct auth type
- For bearer tokens, ensure the token has not expired
- For basic auth, verify username and password are correct
- Check if the API requires additional headers
Requests return errors
Requests return errors
- Check the API documentation for required parameters
- Verify the endpoint path is correct
- Ensure request body format matches expectations
- Look for rate limiting or quota issues
Wrong auth header
Wrong auth header
- Use
headerNameto specify custom header names forheaderauth type - Use
queryParamto specify the query parameter name forqueryauth type - Use
authSchemeto customize the bearer prefix (default: “Bearer”)