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.

4 resources

Browse all access types, or refine the list for your agent.

Refine results 1 selected
Resource type
What do you need?
What can your agent use?
Preparation
Available extra capabilities

Choose an access type to filter by these extras. Otherwise they are saved but do not narrow results.

Select how your agent connects and which extra capabilities it has. Results can match any selected access type. Extra capabilities only filter results when an access type is selected.

Clear filters

Crossref REST API

Retrieve scholarly work metadata by DOI from Crossref's public JSON API.

Reviewed

Listing limitations

  • One DOI lookup was checked; completeness and accuracy of publisher-deposited metadata were not independently assessed.

Retrieve work metadata by DOI

utilityHTTP · GETRead onlyDiscoveryText and data
Preparation

No setup documented

Operation evidence

Action 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.

Open-Meteo

Retrieve weather forecasts for supplied geographic coordinates through a hosted JSON API.

Reviewed

Listing limitations

  • One coordinate and variable combination was checked; commercial access and forecast accuracy were not evaluated.

Get a weather forecast for coordinates

utilityHTTP · GETRead onlyText and data
Preparation

No setup documented

Operation evidence

Action test succeeded · 2026-09-27T12:10:03Z (UTC)

Connection limitations

  • Supply latitude, longitude and selected weather variables; the checked request used a one-day hourly temperature forecast.
  • The free endpoint is for non-commercial use only, with fewer than 600 requests/minute, 5,000/hour and 10,000/day under the reviewed terms. Commercial access uses a separate customer endpoint and key.
  • Weather data is licensed CC BY 4.0 and requires attribution. Availability and forecast accuracy are not guaranteed.
Why these clients fit

HTTP — The documented public forecast uses a GET request without an account or key for non-commercial use.

Web — The documented forecast is a read-only JSON GET using supplied latitude, longitude and selected variables.

Overpass API public instance

Query OpenStreetMap map features using Overpass QL on a public hosted instance.

Reviewed

Listing limitations

  • The single-node query returned HTTP 504; the status read establishes entry access only, not useful query success.

Query OpenStreetMap features

utilityHTTP · GETRead onlyDiscoveryText and data
Preparation

Machine setup1 documented step

Operation evidence

Action 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.

English Wikipedia REST API

Retrieve English Wikipedia page content and metadata through a hosted MediaWiki JSON endpoint.

Reviewed

Listing limitations

  • Only the identified HTTP route was checked; automatic Web-client header compliance and article accuracy remain unverified.

Retrieve page content and metadata

utilityHTTP · GETRead onlyText and data
Preparation

Machine setup1 documented step

Operation evidence

Action test succeeded · 2026-09-27T12:10:04Z (UTC)

Connection limitations

  • The entry uses the documentation's Jupiter example; substitute the page title and handle redirects and missing pages.
  • Wikimedia may block missing or generic User-Agent values. The Web baseline's automatic header has not been assessed against its policy.
  • The checked response declares CC BY-SA 4.0 for the article content. Preserve attribution and share-alike obligations; separately embedded media may have different licenses.
  • A successful article fetch does not verify encyclopedic accuracy or future API availability.
Why these clients fit

HTTP — The documented GET route and client-identifying header fit the HTTP baseline without human setup.