canonical: https://jentic.com/apis/geodservice.com/main # Geodservice GEOD Delivery Boy The GEOD Delivery Boy API is the driver-side backend for a delivery service: a courier signs in with a login and OTP verification, registers an account, and views or updates their profile. Once authenticated, the driver lists the orders assigned to them and changes an order's status by its order id as a delivery progresses. It is a focused fulfillment surface for the last-mile driver, not the customer-facing store. ## For AI agents Authenticate a delivery driver with login and OTP, manage the driver profile, list assigned orders, and update an order's status by its order id. ## Scope Does not handle customer ordering, payment processing, or route mapping. Use for delivery-driver authentication, profile, and order-status updates only. ## Capabilities - Authenticate a delivery driver with a login and OTP verification - Register a new delivery driver account - View and update a delivery driver's profile - List the orders assigned to a delivery driver - Change an order's status by its order id as a delivery progresses ## Use cases ### Agent-assisted delivery dispatch An AI agent supports a courier through a shift: it signs the driver in, pulls the orders assigned to them, and advances each order's status as it is picked up and delivered. Because status changes are keyed to the order id, the agent can update the right delivery without touching the rest of the driver's queue. Example prompt: Sign in the driver, list their assigned orders, and change one order's status to delivered by its order id ### Driver onboarding and profile A new courier needs an account and a verified identity before taking deliveries. The API registers a delivery driver, verifies a one-time passcode at sign-in, and lets the driver view and update their profile, so an agent can run onboarding and keep contact details current without a back-office handoff. Example prompt: Register a new driver, verify their OTP, and set their profile contact details ### Order status tracking for couriers Operations need each delivery's state kept current from the field. The driver lists their assigned orders and changes an order's status as it moves, so an agent can keep the fulfillment record accurate in real time and surface which orders are still outstanding at the end of a run. Example prompt: List a driver's orders and mark the completed ones as delivered while flagging those still in transit ## Key endpoints | Method | Path | Description | | --- | --- | --- | | POST | `/Api/delivery_boy_login` | Log in a delivery driver | | POST | `/Api/delivery_boy_verify_otp` | Verify a driver's OTP | | POST | `/Api/new_delivery_boy_registration` | Register a new delivery driver | | GET | `/Api/view_delivery_boy_profile` | View a driver's profile | | POST | `/Api/update_delivery_boy_profile` | Update a driver's profile | | GET | `/Api/delivery_boy_view_order` | List orders assigned to a driver | | POST | `/Api/change_order_status_by_order_id` | Change an order's status by id | ## Key resources - **Driver authentication** — Login, OTP verification, and registration for a delivery driver - **Driver profile** — View and update a delivery driver's profile - **Orders** — List assigned orders and change an order's status by its order id ## AI readiness 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. - **Score:** 0 / 100 - **Maturity:** Non-Ready - **Dimensions:** - Foundational Compliance: 100 / 100 - Developer Experience & Jentic Compatibility: 72 / 100 - AI-Readiness & Agent Experience: 33 / 100 - Agent Usability: 94 / 100 - Security: 50 / 100 - AI Discoverability: 0 / 100 - **View full report:** https://jentic.com/apis/geodservice.com/main/scorecard - **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/ - **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview ### Score it yourself Every API in the directory is allowlisted, so you can re-score it with no key required. - **Score your own API:** https://jentic.com/scorecard.md - **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md ```sh npx @jentic/api-scorecard-cli score ``` ## Why Jentic - **Setup:** Wiring the GEOD Delivery Boy API by hand means handling the login and OTP flow, carrying the Authorization key, and sequencing the order view before a status change. Through Jentic you install once, import it from the API Directory, store the key once, and your agent calls it. - **Permission scoping:** The order id travels in the request body of the status-change call, so a rule bounds which operations your agent may call, such as the order view and status update. You choose the operations it may call, so driver registration and profile edits are not included unless you add them. - **Credential handling:** Your GEOD key 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. - **Discovery method:** Agents search Jentic by intent such as 'list a driver's orders' or 'change an order status', and Jentic returns the matching operation with its input schema so the agent calls the right endpoint without reading the reference docs. ## Related APIs - **Torod** — Torod handles shipping and delivery logistics as a broader platform than a single driver app. - **Lightspeed** — Lightspeed manages the orders that a delivery driver then fulfills. - **Cratejoy** — Cratejoy produces subscription orders that still need last-mile delivery. ## FAQ ### What authentication does the GEOD Delivery Boy API use? The GEOD Delivery Boy API authenticates with an API key sent in the Authorization header, as declared in its OpenAPI spec, after a driver signs in with a login and one-time passcode. Through Jentic the key is stored encrypted by your own Jentic One instance and injected when a call runs, so it never reaches the agent's prompt or logs. ### Can I update an order's delivery status with this API? Yes. The API changes an order's status by its order id, so an agent can mark a specific delivery picked up or delivered without affecting the rest of a driver's assigned orders. ### What are the rate limits for the GEOD Delivery Boy API? The OpenAPI spec does not specify rate limits. Check the vendor documentation at geodservice.com for current limits before polling order status frequently. ### Is there a GEOD Delivery Boy MCP server? You do not need an MCP server to give your agent the GEOD Delivery Boy API. Jentic connects it directly from the API Directory: import it, store your key once, and your agent signs drivers in and updates order status on demand. ### Can I limit what my agent is allowed to do with the GEOD Delivery Boy API? Yes. Write a rule that allows only the order view and status-change operations, so the agent can read and advance deliveries but cannot register drivers or edit profiles, and every call it makes is logged. ### How do I update an order's status with this API through Jentic? Search Jentic for an intent like 'change a delivery order status' and it returns the matching operation with its input schema, then your agent calls it with the key Jentic injects at runtime. To run it on your own infrastructure, install Jentic One from its GitHub repo.