Grabbly API

Name: Grabbly API
Brand: Grabbly API
Availability: InStock

✓ Official Vendor SpecE CommerceOrder ManagementapiKey2 EndpointsREST

For Agents

Browse available restaurants and place a food order on behalf of a user. Two endpoints cover discovery and order submission.

Install Jentic One Beta

Connect the Grabbly API to your agent

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

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%2Fgrabbly.io%2Fgrabbly" | 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%2Fgrabbly.io%2Fgrabbly" | 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 Grabbly API.

List available restaurants on the Grabbly marketplace via GET /restaurants

Place a food order against a Grabbly restaurant through POST /orders

Submit order line items as part of the POST /orders body

GET STARTED

Start building with Grabbly API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Grabbly API for, with concrete tasks.

★ Conversational Food Ordering Agent

A chat assistant takes 'order me dinner' and walks through GET /restaurants to surface options, then POST /orders to submit the user's chosen items. The published surface is intentionally narrow - there is no menu, modifier, or order-tracking endpoint in the spec - so the agent must work within that scope and ask the user for explicit item details.

Call GET /restaurants, present the list to the user, then POST /orders with the chosen restaurant and item array.

Restaurant Discovery for Local Apps

Local lifestyle and concierge apps query GET /restaurants to populate a 'food nearby' tab without operating their own restaurant database. Refresh on user open or on demand to keep the list current. The endpoint does not include menus or pricing, so apps that need item-level information must fetch that elsewhere.

Call GET /restaurants on app launch and render the response into a card list with the restaurant name and id for downstream order calls.

Voice Assistant Reorder Flow

A voice assistant remembering 'usual order' presents the saved restaurant and items, confirms with the user, and submits POST /orders in one shot. The Grabbly spec does not include a saved-order primitive, so the assistant stores the prior order locally and re-uses the captured restaurant id and item payload to reconstruct the request.

Replay a stored Grabbly order by issuing POST /orders with the cached restaurant_id and items array after voice confirmation.

Agent-Driven Ordering via Jentic

An AI assistant picks up a request like 'order pizza for tonight' and uses Jentic to discover Grabbly's two endpoints. The agent calls /restaurants for options, then /orders to submit. The Authorization API key is held in Jentic's vault, so the agent never handles the raw secret.

Use the Jentic SDK to search 'place a food order', load POST /orders, and execute with the chosen restaurant_id and items list.

Key Endpoints

2 endpoints — grabbly is a food delivery and restaurant marketplace api.

METHOD

PATH

DESCRIPTION

GET

/restaurants

List available restaurants on the Grabbly marketplace

POST

/orders

Place a food order against a chosen restaurant

GET

/restaurants

List available restaurants on the Grabbly marketplace

POST

/orders

Place a food order against a chosen restaurant

Why Jentic?

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

Setup

Wiring the Grabbly API by hand means setting its Authorization API key header and modelling the restaurant discovery and order submission calls yourself. Through Jentic you install once, import Grabbly from the API Directory, store the key once, and your agent calls it.

Permission scoping

Grabbly takes the order details in the request body rather than a resource id in the path, so limit the agent to the operations it needs, such as reading restaurants or submitting an order. You choose the operations it may call, so the agent cannot reach anything you have not included.

Credential isolation

Your Grabbly Authorization API key is stored once, encrypted, by your own Jentic One instance and injected as the header at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'find nearby restaurants' or 'place a food order', and Jentic returns the matching Grabbly operation with its body schema so the agent does not have to model the order shape from scratch.

FAQs

Specific to using Grabbly API through Jentic.

What authentication does the Grabbly API use?

Grabbly uses an API key sent in the Authorization header (security scheme name 'apiKey'). Generate the key in your Grabbly account and send it on every request. Through Jentic, the key is stored in your Jentic One instance and injected into Authorization at execution time so the agent never sees it.

Can I retrieve restaurant menus with this API?

The published OpenAPI spec only exposes GET /restaurants and POST /orders. There is no menu, modifier, or item-pricing endpoint. Agents must obtain item details out-of-band - for example from a partner agreement with the restaurant - before submitting an order body.

What are the rate limits for the Grabbly API?

The OpenAPI spec does not declare rate limits. Limits are enforced at the Grabbly gateway tied to the Authorization key. Cache the /restaurants response for short windows since the list does not change frequently within a session.

How do I place an order through Jentic?

Search Jentic for 'place a food order', load POST /orders, and execute with a restaurant_id plus items array. The Jentic SDK returns the order confirmation payload so the agent can quote the order id and any returned status back to the user.

Can I track an order's delivery status with this API?

The current spec does not expose an order-tracking endpoint. Order tracking, if available, is handled outside this OpenAPI surface. For now, the agent should treat the POST /orders response as the canonical confirmation and prompt the user to track via the Grabbly app or notifications.

Can I limit what my agent is allowed to do with the Grabbly API?

Yes. Because you run Jentic One yourself, you decide which of Grabbly's two operations your agent may call: reading the restaurant list with GET /restaurants, submitting a food order with POST /orders, or both. If you want an agent that only browses and never places orders, grant it GET /restaurants alone, so it cannot reach POST /orders. Since Grabbly takes the order details in the request body rather than a resource id in the path, your rules at the operation level are what control what the agent can actually do.