Felo API PlatformFelo API Platform

AI Tool Setup

Grok Bot

Use Felo Data API search results in Grok Bot. The agent keeps its own model; Felo supplies data for its tasks.

Use Felo Data API search results in Grok Bot. The agent keeps its own model; Felo supplies data for its tasks.

Before you start

Get an API key and check your available credits. This example uses the Tavily search endpoint; other Data APIs have their own parameters and prices.

Set up the application

Grok Bot → cloud computer → terminal → Python tool → private Skill

Connect the data tool

Download the Python helper into the agent’s execution environment. Run configure there yourself, then let the agent run search. The machine must have Python 3.9+ and network access; a key configured on a different computer is not available here.

felo-data-search.py

python3 felo-data-search.py configure
python3 felo-data-search.py search "Felo API Platform documentation"
ToolValue
Namefelo_data_search
Commandpython3 /ABSOLUTE/PATH/felo-data-search.py search "QUERY"
Outputresults[].title, results[].url, results[].content

Data API request

FieldValue
MethodPOST
URLhttps://openapi.felo.ai/v1/beta/tavily/search
AuthorizationBearer YOUR_FELO_API_KEY
OpenAPI credentialX-API-Key: YOUR_FELO_API_KEY
Content-Typeapplication/json
queryFelo API Platform documentation
max_results3
Outputresults[].title, results[].url, results[].content
{
  "query": "Felo API Platform documentation",
  "max_results": 3
}
export FELO_API_KEY='YOUR_FELO_API_KEY'
curl 'https://openapi.felo.ai/v1/beta/tavily/search' \
  -H "Authorization: Bearer $FELO_API_KEY" \
  -H 'Content-Type: application/json' \
  -d '{
  "query": "Felo API Platform documentation",
  "max_results": 3
}'

Verify the integration

Run one search and check for a real results array containing title, url and content. Ask the agent to summarize those results and cite the returned URLs. An empty array is a valid result, not proof of failure. Review the API usage record to confirm the request went through Felo.

Troubleshooting

401: check the key and Authorization header. 402: check credits. 400: check the JSON body and query field. 429 or 5xx: retry with backoff. Save the request_id for support. For Workspace, check script authorization and document sharing; for computer tools, check the key in that execution environment.

Official application documentation