Community OpenAPI document · agent-readyHealthcareClinical Databearer63 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
Create and search blood requests, find eligible blood donors by group and district, check blood inventory shortages, and locate emergency ambulances in Nepal through Raktadan.
Use for: Find O negative blood donors in Kathmandu, Post an urgent blood request for a patient at Bir Hospital, Check whether any district has a critical blood shortage, List emergency ambulances near these coordinates
Not supported: Does not handle electronic health records, hospital appointment booking, or ambulance dispatch payments. Use for Raktadan blood requests, donor matching, inventory, and ambulance lookup in Nepal only.
The Raktadan API runs a blood donation and emergency services platform for Nepal, matching blood requests with eligible donors and listing ambulance services by district. It creates blood requests with the patient's blood group, urgency, and hospital details, searches eligible donors by bloodGroup and district, and lets donors accept or reject a request. It also tracks blood inventory and critical shortages by district, records donations, checks donor eligibility, and finds emergency or nearby ambulances by latitude, longitude, and radius.
Install Jentic One Beta
Connect the Raktadan API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Raktadan API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fraktadan.com%2Fraktadan" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fraktadan.com%2Fraktadan" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with Raktadan API.
Post a blood request with patientName, bloodGroup such as O_NEGATIVE, urgency from LOW to CRITICAL, and hospital contact details
Search eligible blood donors by bloodGroup and district, and list top donors by donations
Accept or reject a blood request as a donor with an availableDate and message
Check blood inventory by district and blood group, and list critical shortages
Find emergency or nearby ambulance services by district or by latitude, longitude, and radius
Check a donor's eligibility from age, lastDonation, and medicalConditions, and record a completed donation
Use Cases
Patterns agents use Raktadan API for, with concrete tasks.
★ Emergency blood-finder agent through Jentic
When a hospital needs a rare blood group fast, an agent can run the search and outreach. Through Jentic the agent searches for 'find blood donors by blood group', receives the matching Raktadan operation with its input schema, and calls GET /api/donors/search with bloodGroup and district, with the JWT bearer token injected at execution time. It can then post a blood request with the hospital details so matched donors can respond.
Search GET /api/donors/search with bloodGroup 'O_NEGATIVE' and district 'Kathmandu', then create a request with POST /api/blood-requests including patientName, patientAge, bloodGroup, urgency 'CRITICAL', hospitalName, hospitalAddress, contactName, and contactPhone
Blood inventory monitoring
Blood banks and health coordinators watch stock levels to plan donation drives. Raktadan returns inventory by district and bloodGroup through GET /api/inventory/district, lists critical shortages through GET /api/inventory/critical, and reports donation and consumption trends over a period through GET /api/inventory/trends.
Call GET /api/inventory/critical, then GET /api/inventory/trends for the affected bloodGroup over the last month, and summarise which districts need a donation drive
Ambulance lookup
Families and responders often need the closest available ambulance. Raktadan lists emergency-available ambulances through GET /api/ambulances/emergency and nearby services through GET /api/ambulances/nearby, both filtered by latitude, longitude, and radius, plus GET /api/ambulances/by-district for a district listing.
Call GET /api/ambulances/nearby with latitude 27.7172, longitude 85.3240, and radius 5, and return the closest services
Donor responses and donation records
Donor platforms close the loop between a request and an actual donation. A donor responds to a request through POST /api/blood-requests/{id}/respond with a response of ACCEPTED or REJECTED, the request's status is updated through PUT /api/blood-requests/{id}/status, and the completed donation is recorded through POST /api/donors/donations.
Respond to blood request 'req_42' with POST /api/blood-requests/{id}/respond using response 'ACCEPTED' and an availableDate
Key Endpoints
63 endpoints — the raktadan api runs a blood donation and emergency services platform for nepal, matching blood requests with eligible donors and listing ambulance services by district.
METHOD
PATH
DESCRIPTION
POST
/api/blood-requests
Create a blood request
GET
/api/donors/search
Search eligible donors
POST
/api/blood-requests/{id}/respond
Respond to a blood request
GET
/api/inventory/critical
List critical blood shortages
GET
/api/ambulances/nearby
Find nearby ambulances
POST
/api/emergency/blood
Emergency blood donor finder
POST
/api/donors/eligibility
Check donation eligibility
POST
/api/blood-requests
Create a blood request
GET
/api/donors/search
Search eligible donors
POST
/api/blood-requests/{id}/respond
Respond to a blood request
GET
/api/inventory/critical
List critical blood shortages
GET
/api/ambulances/nearby
Find nearby ambulances
POST
/api/emergency/blood
Emergency blood donor finder
POST
/api/donors/eligibility
Check donation eligibility
Jentic AI Readiness Score
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
R
Raktadan API
- Foundational (D)45/100
47
Foundational Compliance65
Developer Experience & Jentic Compatibility22
AI-Readiness & Agent Experience92
Agent Usability75
Security63
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.2
Show dimension breakdown
47
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: D+Signals: 4
89%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
0%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
0%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
65
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: BSignals: 4
14%
Example Density
How richly the API is illustrated with examples.
99%
Example Validity
Percentage of examples that conform to their schemas.
47%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
100%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
22
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: FSignals: 4
38%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
0%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
52%
Summary Coverage
Coverage of summaries across operations/tags/info.
92
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: A+Signals: 1
92%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
75
Security
Trust, risk posture, and security compliance.
Grade: A-Signals: 1
75%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
63
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: BSignals: 1
63%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring Raktadan by hand means registering through an OTP flow, logging in for a JWT, attaching it as a bearer token, and handling the admin-only routes separately. Through Jentic you install once, import Raktadan from the API Directory, store the token once, and your agent calls it.
Permission scoping
Raktadan carries most targets, such as blood group and district, in query parameters or the request body, so rules bound which operations your agent may call rather than which donor or district it touches. Limit it to the operations it needs, such as donor and ambulance searches, so bulk notifications and user deactivation are not included unless you add them.
Credential isolation
Your Raktadan token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'find blood donors by blood group' or 'find the nearest ambulance', and Jentic returns the matching Raktadan operation with its input schema, including the bloodGroup and urgency enums, so the agent calls it correctly.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Raktadan API through Jentic.
What authentication does the Raktadan API use?
Per its OpenAPI spec, the Raktadan API authenticates with an HTTP bearer token in JWT format sent in the Authorization header, declared at the top level of the spec. Accounts register through POST /api/auth/register/initiate, which sends an OTP, and POST /api/auth/register/complete, and log in through POST /api/auth/login. Admin-only operations such as POST /api/ambulances and PUT /api/inventory also need an admin role.
Can I search for blood donors by blood group with the Raktadan API?
Yes. GET /api/donors/search takes bloodGroup, using values such as A_POSITIVE or O_NEGATIVE, and district, with page and limit for paging. For urgent cases, POST /api/emergency/blood takes bloodGroup, location, and urgency and is optimised for speed.
What are the rate limits for the Raktadan API?
The OpenAPI spec does not specify rate limits. Check with Raktadan at https://raktadan.com for current limits before running bulk notifications or searches.
Is there a Raktadan MCP server?
You don't need an MCP server to give your agent Raktadan. Jentic connects it directly from the API Directory: import it, store your token once, and your agent calls the donor search, blood request, and ambulance operations on demand.
Can I limit what my agent is allowed to do with the Raktadan API?
Yes. For example, write a rule that allows only GET /api/donors/search, GET /api/inventory/critical, and GET /api/ambulances/nearby, so the agent can look up donors, shortages, and ambulances but cannot send bulk notifications or deactivate users. Every call it makes is logged.
How do I post a blood request through Jentic?
Search Jentic for 'create a blood request', load the POST /api/blood-requests operation, and execute it with patientName, patientAge, bloodGroup, urgency, hospitalName, hospitalAddress, contactName, and contactPhone. To run it on your own infrastructure, install Jentic One from its GitHub repo.
GET STARTED