Ejadtech Sa eManifest API
52
AI ReadinessFoundational (C-)52/100
Community OpenAPI document · agent-readyE CommerceShipping Logisticsbearer19 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
Register the companies, entities, drivers, and vehicles for regulated waste transport, define the waste reference data, then create eManifest requests and issue eManifest certificates.
Use for: Register a new transporter company in the eManifest system, Add a driver and a vehicle before creating a manifest, Create an eManifest request for a waste shipment, Issue an eManifest certificate for a completed movement
Not supported: Does not calculate shipping rates, print carrier labels, or track live vehicle location. Use for registering waste-transport master data and filing eManifest requests and certificates only.
The eManifest API registers the transporter companies, producer entities, waste receivers, branches, drivers, and vehicles behind regulated waste transport, along with the reference data they depend on such as waste types, waste classifications, container types, units of measure, and handling methods. On top of that master data it creates eManifest requests for a waste movement and issues eManifest certificates for it, and it reads supporting lists such as states and process activities. A token endpoint issues the bearer credential each call carries.
Install Jentic One Beta
Connect the eManifest API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the eManifest 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%2Fejadtech.sa%2Femanifest" | 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%2Fejadtech.sa%2Femanifest" | 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 eManifest API.
Register transporter companies, producer entities, and waste receivers
Add drivers, vehicles, vehicle categories, and vehicle activities to the fleet
Define waste types, waste classifications, container types, and handling methods
Create eManifest requests for a waste movement
Issue eManifest certificates for a completed manifest
Read supporting reference lists such as states and process activities
Use Cases
Patterns agents use eManifest API for, with concrete tasks.
★ Agent-filed waste manifests
An AI agent files the paperwork for a waste movement. Through Jentic the agent confirms the transporter, producer, driver, and vehicle records exist, creates an eManifest request for the movement, and issues the eManifest certificate once it is ready. The waste type, classification, and handling-method reference data back each record.
Create an eManifest request for a waste movement and issue its eManifest certificate once the request is accepted
Onboarding a transporter's fleet
Before a transporter can move waste, its fleet must be on record. The API registers the transporter company, its branches, drivers, and vehicles, and ties them to vehicle categories and activities, so an onboarding workflow can stand up a new transporter's data in sequence rather than through a manual portal.
Register a transporter company, then add its branches, drivers, and vehicles with their vehicle categories
Setting up waste reference data
A new deployment needs its catalogs populated first. The API defines waste types, waste classifications, container types, units of measure, and handling methods, and reads lists such as states and process activities, so the reference data every manifest depends on is in place before any request is created.
Create the waste types, classifications, and handling methods, then read back the process activities list
Key Endpoints
19 endpoints — the emanifest api registers the transporter companies, producer entities, waste receivers, branches, drivers, and vehicles behind regulated waste transport, along with the reference data they depend on such as waste types, waste classifications, container types, units of measure, and handling methods.
METHOD
PATH
DESCRIPTION
POST
/api/emanifest/create_transporter_companies
Register a transporter company
POST
/api/emanifest/create_drivers
Add a driver
POST
/api/emanifest/create_vehicles
Add a vehicle
POST
/api/emanifest/create_emanifest_requests
Create an eManifest request
POST
/api/emanifest/create_emanifest_certificates
Issue an eManifest certificate
POST
/api/emanifest/create_waste_types
Define a waste type
GET
/api/emanifest/get_states
Get the list of states
GET
/api/emanifest/get_process_activities
Get the process activities list
POST
/api/emanifest/create_transporter_companies
Register a transporter company
POST
/api/emanifest/create_drivers
Add a driver
POST
/api/emanifest/create_vehicles
Add a vehicle
POST
/api/emanifest/create_emanifest_requests
Create an eManifest request
POST
/api/emanifest/create_emanifest_certificates
Issue an eManifest certificate
POST
/api/emanifest/create_waste_types
Define a waste type
GET
/api/emanifest/get_states
Get the list of states
GET
/api/emanifest/get_process_activities
Get the process activities list
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.
E
eManifest API Collection
- Foundational (C-)52/100
74
Foundational Compliance78
Developer Experience & Jentic Compatibility34
AI-Readiness & Agent Experience94
Agent Usability60
Security30
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.2
Show dimension breakdown
74
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: A-Signals: 4
95%
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).
100%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
78
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: A-Signals: 4
93%
Example Density
How richly the API is illustrated with examples.
94%
Example Validity
Percentage of examples that conform to their schemas.
25%
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.
34
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: FSignals: 4
6%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
95%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
33%
Summary Coverage
Coverage of summaries across operations/tags/info.
94
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: A+Signals: 1
94%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
60
Security
Trust, risk posture, and security compliance.
Grade: B-Signals: 1
60%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
30
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: FSignals: 1
30%
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 the eManifest API by hand means obtaining a bearer token from its token endpoint, choosing between its production and test hosts, and populating a chain of master data before a manifest will file. Through Jentic you install once, import eManifest from the API Directory, store the token once, and your agent calls it.
Permission scoping
The eManifest API carries each record in the request body rather than a URL path, so a rule bounds your agent to the operations it needs: it can register drivers and vehicles and create manifest requests while issuing certificates stays out unless you add it. Rules bound which operations the agent may call, not which record.
Credential isolation
Your eManifest token is stored once, encrypted, by your own Jentic One instance and injected when a call runs. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'register a transporter company' or 'create a waste manifest', and Jentic returns the matching eManifest operation with its input schema so the agent calls the right endpoint without reading the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using eManifest API through Jentic.
What authentication does the eManifest API use?
The eManifest API authenticates with a bearer token per its OpenAPI spec: you obtain a token from its token endpoint and send it as `Authorization: Bearer ...` on each operation. Through Jentic the token is stored encrypted by your own Jentic One instance and injected at call time, so it never enters the agent's context.
Is there an eManifest MCP server?
You don't need an MCP server to give your agent the eManifest API. Jentic connects it directly from the API Directory: import it, store your token once, and your agent calls the registration and manifest operations on demand without loading another server's tool definitions into its context.
Can I file a waste manifest with the eManifest API?
Yes. After the producer entities, waste receivers, transporter companies, drivers, and vehicles are registered, you create an eManifest request for the movement and then issue an eManifest certificate for it. Reference lists such as states, waste types, and handling methods back those records.
What are the rate limits for the eManifest API?
The OpenAPI spec does not state rate limits. Check with the Saudi eManifest system operator at https://mwan.gov.sa for the limits that apply to your integration before running bulk registration.
Can I limit what my agent is allowed to do with the eManifest API?
Yes. Write a rule that allows only the operations your agent needs, such as registering drivers and vehicles and creating manifest requests, and leave certificate issuance out of the allowed set unless the agent must issue them. Every call it makes is logged.
How do I create a waste manifest with the eManifest API through Jentic?
Search Jentic for 'create a waste manifest request' and it returns the request operation with its input schema; your agent supplies the movement details and then issues the certificate. To run it on your own infrastructure, install Jentic One from its GitHub repo.
GET STARTED