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 a Lybrate doctors categorized services, procedures, sub-specialities, and expertise areas from https://lybrate.com while preserving every non-empty source field.
Returns a Lybrate doctors categorized services, procedures, sub-specialities, and expertise areas from https://lybrate.com while preserving every non-empty source field. It runs on Notte's browser infrastructure and returns structured JSON, so you can call it like any other API — pass city, doctor_username, 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/d557396c-93d3-4f37-8265-c49f5af3fcb9/runs/start' \
--header 'x-notte-api-key: YOUR_API_KEY' \
--header 'Content-Type: application/json' \
--header 'Authorization: Bearer YOUR_API_KEY' \
--data '{
"function_id": "d557396c-93d3-4f37-8265-c49f5af3fcb9",
"variables": {
"city": "delhi",
"doctor_username": "dr-suruchi-puri-dermatologist",
"timeout_seconds": 20
}
}'{
"city": "<string>",
"services": [
{
"enabled": true,
"hideUrl": true,
"pageUrl": "<string>",
"treatmentName": "<string>",
"healthCorpusId": 0
}
],
"procedures": [
{
"enabled": true,
"hideUrl": true,
"pageUrl": "<string>",
"treatmentName": "<string>",
"healthCorpusId": 0
}
],
"source_url": "<string>",
"doctor_name": "<string>",
"service_count": 0,
"doctor_username": "<string>",
"expertise_areas": [
{
"id": 0,
"name": "<string>",
"pageUrl": "<string>",
"displayName": "<string>",
"srpDisplayName": "<string>"
}
],
"procedure_count": 0,
"sub_specialities": [
{
"id": 0,
"name": "<string>",
"pageUrl": "<string>",
"clinicSpecialityId": 0
}
],
"expertise_area_count": 0,
"sub_speciality_count": 0
}