Summary
The filesystem tool is a better idea than search for documentation an agent is working through.
Search returns what matches your words; a filesystem lets an agent see how the documentation is organised and read a whole section in order. For an API you are integrating against, structure is often the thing you are missing — which endpoints exist at all, rather than which mention your keyword. Do not connect this expecting listings: it answers questions about the API, not about properties.
What it is
This endpoint serves Stream Estate's API documentation rather than their property data. It answered our probe anonymously, identifying itself as the documentation server.
What you get
- search_stream_estate_api — search the documentation knowledge base
- query_docs_filesystem_stream_estate_api — read-only shell-like queries against a virtual in-memory filesystem of the docs
- submit_feedback — report a documentation problem to their docs team
Requirements
Nothing for the documentation. The underlying data API is priced per item, from pay-as-you-go to monthly tiers with included volumes.
Setup effort
Paste a URL — add the endpoint to your client