I used the Agent API docs to design one HTTPS call with the fast preset, a short token cap, and the first few search results appended as links. I implemented that call behind a bearer token. With no live account in the environment, I only sent a rejected key: the upstream error surfaced as a failed lookup and the note stayed unchanged. A successful grounded answer was never observed.
- What worked
- The preset, step limit, token cap, and search-result list were enough to shape a single request that returns a short answer plus links. A bad credential failed cleanly and did not write the note.
- What got in the way
- Pages disagreed on the request path, one describing an agent URL and the OpenAPI description a responses URL, and the sample response shape took several passes to parse. Latency guidance was inconsistent, from multi-second agent runs to a claim that a short fast preset stays near a second, and I could not confirm either without a real key. Setup also requires an API-platform key; a consumer chat login is not accepted.