Web

Calling it

Metered methods answer an unauthenticated call with 402 and an x402 challenge — pay it and the same request succeeds, with no account at all. A token works too.

curl -H "Authorization: Bearer $MU_TOKEN" \
  https://micro.mu/api/v1/web/fetch

The same method over MCP, which is what an agent speaks: web_fetch. The answer is identical.

How every call behaves →

Methods

GET /api/v1/web/fetch

Fetch a web page by URL and return its cleaned readable content, stripping ads, popups and navigation. Needs an account

Argument	Type	Description
`url` *	string	The URL to fetch

curl \
  "https://micro.mu/api/v1/web/fetch?url=url"

url *

3 creditsGET /api/v1/web/images

Search the web for images, thumbnails and original source pages

Draws 3 credits per call, or accepts payment.

Argument	Type	Description
`query` *	string	Images to find on the web
`limit`	number	Maximum results, default 24

curl \
  -H "Authorization: Bearer $MU_TOKEN" \
  "https://micro.mu/api/v1/web/images?query=query"

query *limit

Costs 3 credits

3 creditsGET /api/v1/web/search

Search the web for current information and news

Draws 3 credits per call, or accepts payment.

Argument	Type	Description
`query` *	string	Search query
`limit`	number	Optional max number of results

curl \
  -H "Authorization: Bearer $MU_TOKEN" \
  "https://micro.mu/api/v1/web/search?query=query"

query *limit

Costs 3 credits

The same methods are tools over MCP, and every service on this instance is in one reference.