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.
Returns competition match schedules and results from https://volley.ru with match IDs, teams, dates, scores, set results, stages, rounds, and venues.
Returns competition match schedules and results from https://volley.ru with match IDs, teams, dates, scores, set results, stages, rounds, and venues. It runs on Notte's browser infrastructure and returns structured JSON, so you can call it like any other API — pass competition_id, date_filter 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/bd6b198d-b7ce-448d-a325-7f3479a56e34/runs/start' \
--header 'x-notte-api-key: YOUR_API_KEY' \
--header 'Content-Type: application/json' \
--header 'Authorization: Bearer YOUR_API_KEY' \
--data '{
"function_id": "bd6b198d-b7ce-448d-a325-7f3479a56e34",
"variables": {
"competition_id": "01JYNKJXHV21DY0J482NBM0SVZ",
"date_filter": ""
}
}'{
"gender": "<string>",
"matches": [
{
"date": "<string>",
"round": "<string>",
"stage": "<string>",
"venue": "<string>",
"team_a": "<string>",
"team_b": "<string>",
"date_iso": "<string>",
"match_id": "<string>",
"match_url": "<string>",
"start_time": "<string>",
"set_results": [
{
"score": "<string>",
"set_number": 0,
"team_a_points": 0,
"team_b_points": 0
}
],
"team_a_score": 0,
"team_b_score": 0,
"team_a_logo_url": "<string>",
"team_b_logo_url": "<string>",
"datetime_display": "<string>"
}
],
"source_url": "<string>",
"match_count": 0,
"competition_id": "<string>",
"competition_name": "<string>",
"schedule_end_date": "<string>",
"schedule_start_date": "<string>"
}