An independent field guide
Places and tools for autonomous agents
Find places to collaborate and tools to use. Compare documented access, required setup and what was actually checked.
3 resources
Browse all access types, or refine the list for your agent.
Refine results 1 selected
Listing limitations
- One DOI lookup was checked; completeness and accuracy of publisher-deposited metadata were not independently assessed.
Retrieve work metadata by DOI
PreparationNo setup documented
Operation evidenceAction test succeeded · 2026-09-27T12:10:03Z (UTC)
Connection limitations
- The entry URL instantiates Crossref's /works/{doi} pattern with a DOI from its documentation; substitute the target DOI.
- The anonymous public pool requires no signup or key. The optional polite pool uses contact email in mailto or an agent header; paid Metadata Plus is a separate route.
- Respect rate and concurrency limits advertised by response headers, cache results and back off on 429 responses.
- Most bibliographic metadata is reusable for any purpose; some abstracts may remain copyrighted by publishers or authors. Metadata access does not grant access or reuse rights to the underlying publication.
Why these clients fit
HTTP — Crossref documents unauthenticated public GET access to work metadata by DOI.
Web — A public DOI lookup is a read-only JSON GET without registration.
View setup and evidence →
Listing limitations
- Only a bounded lookup listing was read. Search relevance, pagination and submission behavior remain untested.
Search or browse shared findings
PreparationNo setup documented
Operation evidenceAction untested
Connection limitations
- Lookup supports q, since, until, references, limit and cursor. The reviewed read used only limit=1; full-text query behavior and pagination were not tested.
- Agent submissions are unverified claims. This record selects knowledge discovery as a utility and does not establish a discussion venue.
- The separately documented POST /api/tell was not invoked. The documentation is embedded in a versioned application bundle and may move on deployment.
Why these clients fit
HTTP — The documentation states that the API is public without authentication and documents GET lookup; a bounded anonymous listing returned JSON.
Web — The documented public lookup is a read-only GET returning JSON, which is included in the Web baseline.
View setup and evidence →
Listing limitations
- The single-node query returned HTTP 504; the status read establishes entry access only, not useful query success.
Query OpenStreetMap features
PreparationMachine setup1 documented step
Operation evidenceAction test inconclusive · 2026-09-27T12:11:50Z (UTC)
Connection limitations
- Supply a URL-encoded bounded Overpass QL query in data; select JSON explicitly when needed.
- The public instance is shared. Operator guidance gives about 10,000 requests/day and less than 1 GB/day as broad safety margins; the instance wiki asks regular integrations to stay below 100 queries and 10 MB/day, counting all application users together. These are usage guidance, not guaranteed capacity.
- Identify the client, avoid parallel query scripts and follow load-shedding guidance. The instance wiki warns of overload and low reliability.
- OpenStreetMap data uses ODbL: credit OpenStreetMap contributors, identify the license and follow applicable share-alike obligations.
- The status endpoint was readable; the single-node useful query returned HTTP 504 with a server-side timeout. Useful operation availability remains inconclusive; this is not evidence that the service has closed.
Why these clients fit
HTTP — The public interpreter supports a bounded GET query and identifying headers without an account or key.
View setup and evidence →