APIs your agents can find on their own.
Point a client at it and your agent searches this marketplace before it builds anything. Hit, and it runs it. Miss, and it describes what it needs — then gets a typed function back.
Builds started here are published automatically with their source code. Other users can run, download and fork them. Check your build instructions for private information. Unpublishing cannot retract downloaded or forked copies.
Searches editorial content on https://ucas.com with content-type filtering and pagination, returning complete non-empty records with titles, URLs, summaries, and authors.
Searches editorial content on https://ucas.com with content-type filtering and pagination, returning complete non-empty records with titles, URLs, summaries, and authors. It runs on Notte's browser infrastructure and returns structured JSON, so you can call it like any other API — pass query, content_type, page, page_size, timeout_seconds and get the result back without maintaining a scraper.
Hand the whole endpoint to Claude Code or any MCP client instead of writing the call yourself.
curl --location 'https://us-prod.notte.cc/functions/632dd5a8-63d1-44a4-9eaf-710dcf8236e6/runs/start' \
--header 'x-notte-api-key: YOUR_API_KEY' \
--header 'Content-Type: application/json' \
--header 'Authorization: Bearer YOUR_API_KEY' \
--data '{
"function_id": "632dd5a8-63d1-44a4-9eaf-710dcf8236e6",
"variables": {
"query": "psychology",
"content_type": "all",
"page": 1,
"page_size": 10,
"timeout_seconds": 20
}
}'{
"page": 0,
"query": "<string>",
"results": [
{
"url": "<string>",
"type": "<string>",
"title": "<string>",
"author": "<string>",
"status": true,
"created": 0,
"summary": "<string>",
"objectID": "<string>",
"node_image": "<string>",
"relative_url": "<string>",
"image_file_fid": 0,
"image_file_uuid": "<string>",
"image_file_tile_url": "<string>",
"related_scheme_name": [
"<string>"
],
"related_audience_name": [
"<string>"
]
}
],
"page_size": 0,
"total_pages": 0,
"content_type": "<string>",
"total_results": 0,
"available_content_types": {
"webform": 0,
"landing_page": 0,
"structure_content": 0
}
}