Install Jentic One Beta

Connect the GEOD Delivery Boy to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the GEOD Delivery Boy, 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.

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%2Fgeodservice.com%2Fmain" | sh

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%2Fgeodservice.com%2Fmain" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic 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 GEOD Delivery Boy API.

Authenticate a delivery driver with a login and OTP verification

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

GET STARTED

Start building with GEOD Delivery Boy API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use GEOD Delivery Boy API for, with concrete tasks.

★ 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.

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.

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.

List a driver's orders and mark the completed ones as delivered while flagging those still in transit

Key Endpoints

7 endpoints — 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.

METHOD

PATH

DESCRIPTION

POST

/Api/delivery_boy_login

POST

/Api/delivery_boy_verify_otp

Verify a driver's OTP

POST

/Api/new_delivery_boy_registration

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

POST

/Api/delivery_boy_login

POST

/Api/delivery_boy_verify_otp

Verify a driver's OTP

POST

/Api/new_delivery_boy_registration

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

Why Jentic?

What agents get from Jentic-routed access to this vendor.

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 isolation

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.

Intent-based discovery

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.

FAQs

Specific to using GEOD Delivery Boy API through Jentic.

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.

Geodservice GEOD Delivery Boy

AI ReadinessNon-Ready (F)0/100

See full scorecard

Community OpenAPI document · agent-readyE CommerceOrder ManagementapiKey7 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For 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.

Use for: Log in a delivery driver with their credentials, Verify a delivery driver's one-time passcode, Register a new delivery driver account, View the profile of a delivery driver

Not supported: Does not handle customer ordering, payment processing, or route mapping. Use for delivery-driver authentication, profile, and order-status updates only.

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.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

100

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A+Signals: 4

99%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

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.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: A-Signals: 4

64%

Example Density

How richly the API is illustrated with examples.

100%

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.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: FSignals: 4

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

71%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

50%

Summary Coverage

Coverage of summaries across operations/tags/info.

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.

Security

Trust, risk posture, and security compliance.

Grade: C-Signals: 1

50%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: FSignals: 1

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the GEOD Delivery Boy to your agent

Capabilities

Start building with GEOD Delivery Boy API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Geodservice GEOD Delivery Boy

Jentic AI Readiness Score

GEOD Delivery Boy

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness