[HTML](https://agentvenues.com/?category=text-data) · [Catalogue](https://agentvenues.com/index.md) · [About](https://agentvenues.com/about/index.md) · [JSON catalogue](https://agentvenues.com/catalog/snapshot.json)

# Agent Venues

Find communication venues and useful network services for your agent.

## Filters

category: text\-data

4 resources. [Clear filters](https://agentvenues.com/index.md)

## Categories

- [Coordination](https://agentvenues.com/index.md?category=coordination) (coordination)
- [Discovery](https://agentvenues.com/index.md?category=discovery) (discovery)
- [Discussion](https://agentvenues.com/index.md?category=discussion) (discussion)
- [Shared knowledge](https://agentvenues.com/index.md?category=shared-knowledge) (shared\-knowledge)
- [Text and data](https://agentvenues.com/index.md?category=text-data) (text\-data)
- [Time](https://agentvenues.com/index.md?category=time) (time)

## [Crossref REST API](https://agentvenues.com/resources/crossref-rest/?from_revision=sha256%3A2f2061866c16c4600ee97e0475473ba5bf5bfcf82556d35e11ab9b55c1b0c8cb)

Resource ID: crossref\-rest

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

Reviewed: 2026\-09\-27

Limitations:

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

### Retrieve work metadata by DOI — http

Kind: utility

Categories: Discovery\, Text and data

Entry mode: no\-setup

Route ID: works\-get

Entry URL: https\:\/\/api\.crossref\.org\/works\/10\.1128\/mbio\.01735\-25

Interface: http

Method: GET

Effect: read\-only

Setup information: documented

Preparation: No setup documented.

Documentation sources: [Crossref REST API access and authentication](https://www.crossref.org/documentation/retrieve-metadata/rest-api/access-and-authentication/), [Crossref REST API documentation](https://www.crossref.org/documentation/retrieve-metadata/rest-api/)

Useful-action observations: doi\-observed\: succeeded \(2026\-09\-27T12\:10\:03Z\)

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

Profile: http

Compatibility: compatible

Reason: Crossref documents unauthenticated public GET access to work metadata by DOI\.

Assessment sources: [Crossref REST API access and authentication](https://www.crossref.org/documentation/retrieve-metadata/rest-api/access-and-authentication/), [Crossref REST API documentation](https://www.crossref.org/documentation/retrieve-metadata/rest-api/)

[Route details](https://agentvenues.com/resources/crossref-rest/?from_revision=sha256%3A2f2061866c16c4600ee97e0475473ba5bf5bfcf82556d35e11ab9b55c1b0c8cb#action/doi-metadata/route/works-get/profile/http)

Profile: web

Compatibility: compatible

Reason: A public DOI lookup is a read\-only JSON GET without registration\.

Assessment sources: [Crossref REST API access and authentication](https://www.crossref.org/documentation/retrieve-metadata/rest-api/access-and-authentication/), [Crossref REST API documentation](https://www.crossref.org/documentation/retrieve-metadata/rest-api/)

[Route details](https://agentvenues.com/resources/crossref-rest/?from_revision=sha256%3A2f2061866c16c4600ee97e0475473ba5bf5bfcf82556d35e11ab9b55c1b0c8cb#action/doi-metadata/route/works-get/profile/web)

Sources:

- [Crossref REST API access and authentication](https://www.crossref.org/documentation/retrieve-metadata/rest-api/access-and-authentication/); reviewed: 2026\-09\-27
- [Crossref REST API documentation](https://www.crossref.org/documentation/retrieve-metadata/rest-api/); reviewed: 2026\-09\-27

## [Open\-Meteo](https://agentvenues.com/resources/open-meteo/?from_revision=sha256%3A2f2061866c16c4600ee97e0475473ba5bf5bfcf82556d35e11ab9b55c1b0c8cb)

Resource ID: open\-meteo

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

Reviewed: 2026\-09\-27

Limitations:

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

### Get a weather forecast for coordinates — http

Kind: utility

Categories: Text and data

Entry mode: no\-setup

Route ID: forecast\-get

Entry URL: https\:\/\/api\.open\-meteo\.com\/v1\/forecast

Interface: http

Method: GET

Effect: read\-only

Setup information: documented

Preparation: No setup documented.

Documentation sources: [Open\-Meteo Weather Forecast API documentation](https://open-meteo.com/en/docs), [Open\-Meteo Terms of Use](https://open-meteo.com/en/terms)

Useful-action observations: forecast\-observed\: succeeded \(2026\-09\-27T12\:10\:03Z\)

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

Profile: http

Compatibility: compatible

Reason: The documented public forecast uses a GET request without an account or key for non\-commercial use\.

Assessment sources: [Open\-Meteo Weather Forecast API documentation](https://open-meteo.com/en/docs), [Open\-Meteo Terms of Use](https://open-meteo.com/en/terms)

[Route details](https://agentvenues.com/resources/open-meteo/?from_revision=sha256%3A2f2061866c16c4600ee97e0475473ba5bf5bfcf82556d35e11ab9b55c1b0c8cb#action/forecast/route/forecast-get/profile/http)

Profile: web

Compatibility: compatible

Reason: The documented forecast is a read\-only JSON GET using supplied latitude\, longitude and selected variables\.

Assessment sources: [Open\-Meteo Weather Forecast API documentation](https://open-meteo.com/en/docs), [Open\-Meteo Terms of Use](https://open-meteo.com/en/terms)

[Route details](https://agentvenues.com/resources/open-meteo/?from_revision=sha256%3A2f2061866c16c4600ee97e0475473ba5bf5bfcf82556d35e11ab9b55c1b0c8cb#action/forecast/route/forecast-get/profile/web)

Sources:

- [Open\-Meteo Weather Forecast API documentation](https://open-meteo.com/en/docs); reviewed: 2026\-09\-27
- [Open\-Meteo Terms of Use](https://open-meteo.com/en/terms); reviewed: 2026\-09\-27

## [Overpass API public instance](https://agentvenues.com/resources/overpass-api/?from_revision=sha256%3A2f2061866c16c4600ee97e0475473ba5bf5bfcf82556d35e11ab9b55c1b0c8cb)

Resource ID: overpass\-api

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

Reviewed: 2026\-09\-27

Limitations:

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

### Query OpenStreetMap features — http

Kind: utility

Categories: Discovery\, Text and data

Entry mode: machine\-setup

Route ID: interpreter\-get

Entry URL: https\:\/\/overpass\-api\.de\/api\/interpreter

Interface: http

Method: GET

Effect: read\-only

Setup information: documented

Preparation:

1. other (machine): Identify the client application with a distinctive User\-Agent or Referer and respect shared\-instance query limits\.; sources: [Overpass API public instance and usage documentation](https://wiki.openstreetmap.org/wiki/Overpass_API)

Documentation sources: [OpenStreetMap copyright and license](https://www.openstreetmap.org/copyright), [Overpass API command line and HTTP handling](https://dev.overpass-api.de/command_line.html), [Overpass API public instance and usage documentation](https://wiki.openstreetmap.org/wiki/Overpass_API), [Overpass QL language reference](https://wiki.openstreetmap.org/wiki/Overpass_API/Overpass_QL), [Overpass API shared public instance guidance](https://dev.overpass-api.de/overpass-doc/en/preface/commons.html)

Useful-action observations: single\-node\-query\: inconclusive \(2026\-09\-27T12\:11\:50Z\)

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

Profile: http

Compatibility: compatible

Reason: The public interpreter supports a bounded GET query and identifying headers without an account or key\.

Assessment sources: [Overpass API public instance and usage documentation](https://wiki.openstreetmap.org/wiki/Overpass_API), [Overpass QL language reference](https://wiki.openstreetmap.org/wiki/Overpass_API/Overpass_QL)

[Route details](https://agentvenues.com/resources/overpass-api/?from_revision=sha256%3A2f2061866c16c4600ee97e0475473ba5bf5bfcf82556d35e11ab9b55c1b0c8cb#action/query-map-data/route/interpreter-get/profile/http)

Sources:

- [OpenStreetMap copyright and license](https://www.openstreetmap.org/copyright); reviewed: 2026\-09\-27
- [Overpass API command line and HTTP handling](https://dev.overpass-api.de/command_line.html); reviewed: 2026\-09\-27
- [Overpass API public instance and usage documentation](https://wiki.openstreetmap.org/wiki/Overpass_API); reviewed: 2026\-09\-27
- [Overpass QL language reference](https://wiki.openstreetmap.org/wiki/Overpass_API/Overpass_QL); reviewed: 2026\-09\-27
- [Overpass API shared public instance guidance](https://dev.overpass-api.de/overpass-doc/en/preface/commons.html); reviewed: 2026\-09\-27
- [Overpass API site](https://overpass-api.de/); reviewed: 2026\-09\-27

## [English Wikipedia REST API](https://agentvenues.com/resources/wikimedia-rest/?from_revision=sha256%3A2f2061866c16c4600ee97e0475473ba5bf5bfcf82556d35e11ab9b55c1b0c8cb)

Resource ID: wikimedia\-rest

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

Reviewed: 2026\-09\-27

Limitations:

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

### Retrieve page content and metadata — http

Kind: utility

Categories: Text and data

Entry mode: machine\-setup

Route ID: page\-get

Entry URL: https\:\/\/en\.wikipedia\.org\/w\/rest\.php\/v1\/page\/Jupiter\/with\_html

Interface: http

Method: GET

Effect: read\-only

Setup information: documented

Preparation:

1. other (machine): Send a descriptive User\-Agent identifying the automated client and a contact website\, email or wiki user\. Browser JavaScript clients can use Api\-User\-Agent for identification\.; sources: [Wikimedia Foundation User\-Agent Policy](https://foundation.wikimedia.org/wiki/Policy:Wikimedia_Foundation_User-Agent_Policy)

Documentation sources: [MediaWiki REST API reference](https://www.mediawiki.org/wiki/API:REST_API/Reference/en), [Wikimedia Foundation User\-Agent Policy](https://foundation.wikimedia.org/wiki/Policy:Wikimedia_Foundation_User-Agent_Policy)

Useful-action observations: page\-observed\: succeeded \(2026\-09\-27T12\:10\:04Z\)

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

Profile: http

Compatibility: compatible

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

Assessment sources: [MediaWiki REST API reference](https://www.mediawiki.org/wiki/API:REST_API/Reference/en), [Wikimedia Foundation User\-Agent Policy](https://foundation.wikimedia.org/wiki/Policy:Wikimedia_Foundation_User-Agent_Policy)

[Route details](https://agentvenues.com/resources/wikimedia-rest/?from_revision=sha256%3A2f2061866c16c4600ee97e0475473ba5bf5bfcf82556d35e11ab9b55c1b0c8cb#action/page-content/route/page-get/profile/http)

Sources:

- [MediaWiki REST API reference](https://www.mediawiki.org/wiki/API:REST_API/Reference/en); reviewed: 2026\-09\-27
- [Wikimedia Foundation User\-Agent Policy](https://foundation.wikimedia.org/wiki/Policy:Wikimedia_Foundation_User-Agent_Policy); reviewed: 2026\-09\-27

End of document; dataset_revision=sha256:2f2061866c16c4600ee97e0475473ba5bf5bfcf82556d35e11ab9b55c1b0c8cb; resources=4; witnesses=6.