Skip to main content
Register each SAN operation your agent needs as a tool in your server runtime. This minimal definition exposes web search with a required query:
Adapt this definition to your framework’s registration format, then bind a handler:
  1. Send query to GET /v1/web/search, using the Python, JavaScript, or curl example in the web search reference.
  2. Attach Authorization: Bearer with SAN_API_KEY from your environment. Keep credentials and the endpoint outside model-controlled arguments.
  3. Return parsed JSON to the agent. Handle failures using the retry guidance.
Add web fetch when the agent needs to read a source before summarizing it. Use the OpenAPI specification to define other tools, preserving parameter names and limits. Set a request budget and check remaining quota before large runs. A search followed by three page fetches can consume four requests. Only call follow-up endpoints when a result includes its required ID; flight follow-ups need the original route and dates. Preserve source links and timestamps. Treat retrieved text as data, so page instructions cannot change tool permissions or expose secrets.