Skip to main content
The HTTP capability is a “swiss army knife” that allows agents to interact with any REST API.

​
Why HTTP?

HTTP is the universal interface for the internet. This capability allows agents to:
  • Interact with any REST API
  • Build integrations on the fly
  • Work with services without native integrations
  • Create custom workflows
HTTP capability is like a magic wand — it enables agents to interact with virtually any online service.

​
Available Methods

MethodUse Case
GETRetrieve data from APIs
POSTCreate records, submit forms
PUTUpdate existing records
DELETERemove records
PATCHPartial updates

​
Authentication

Many APIs require authentication. You can provide:
  • API Keys — Stored securely as credentials
  • Bearer Tokens — OAuth tokens for authorized access
  • Basic Auth — Username/password combinations
  • Custom Headers — Any authentication scheme
Credentials are encrypted and stored securely. They are never exposed to the LLM directly — the platform handles authentication.

​
Real-World Example

When evaluating potential office locations, an agent used HTTP capability to:
1

Import data

Imported employee addresses and potential locations.
2

Geocoding

Used a public API to convert addresses to GPS coordinates.
3

Transit calculation

Used another API to calculate journey times.
4

Map generation

Generated an interactive map visualization.

​
Best Practices

Point the agent to API documentation so it understands available endpoints.
Start with simple API calls before building complex workflows.
Instruct agents on how to handle API errors and rate limits.
Always use the credential system rather than putting keys in instructions.