canonical: https://jentic.com/apis/compassdigital.org/compassdigital # Compassdigital P&G Integration Edge Service The P&G Integration Edge Service powers food-service ordering for P&G locations: it issues a user token, returns location and menu details, builds and updates a cart, and places and retrieves orders. Use it to drive a mobile or kiosk ordering flow through a single edge integration. ## For AI agents Authenticate a user, look up locations and menus, build and update a cart, and place and retrieve orders through the P&G Integration Edge Service. ## Scope Does not process payments, manage inventory, or handle delivery logistics. Use for P&G location, menu, cart, and order operations only. ## Capabilities - Exchange basic credentials for a user access token - Retrieve a location and its menu by id - Create a cart and update the items in it - Place an order from a cart - Retrieve an order by its id ## Use cases ### AI agent food ordering An AI agent takes a food order end to end: it authenticates the user, looks up the location menu, builds a cart, and submits the order. Through Jentic the agent finds the menu, cart, and order operations by intent and calls them with the stored credentials, without wiring the token exchange itself. Example prompt: Look up the lunch menu for a location, add two items to a cart, and place the order ### Kiosk order automation A self-service kiosk builds a cart from the on-screen menu and submits the order to the edge service when the customer checks out. The API separates cart updates from order placement so the kiosk can adjust items before committing the order. Example prompt: Create a cart, add the selected items, and submit the order for the current location ### Order status tracking After an order is placed, a tracking view retrieves the order by its id to show progress to the customer. The API returns the order details so a workflow can poll and surface status without a separate system. Example prompt: Retrieve an order by its id and report its current status ## Key endpoints | Method | Path | Description | | --- | --- | --- | | POST | `/edge/pg/user/token` | Get a user access token | | GET | `/edge/pg/location/{location_id}` | Get a location | | GET | `/edge/pg/menu/{menu_id}` | Get a menu | | POST | `/edge/pg/cart` | Create a cart | | PUT | `/edge/pg/cart/{cart_id}/items` | Update cart items | | POST | `/edge/pg/order` | Place an order | ## Key resources - **Locations and menus** — Retrieve a location and its menu by id - **Carts** — Create a cart and update the items in it - **Orders** — Place an order from a cart and retrieve an order by id ## Why Jentic - **Setup:** Calling the P&G Integration Edge Service by hand means first exchanging basic credentials for a bearer token, then carrying that token on every cart and order call. Through Jentic you install once, import the API, store both the basic and bearer credentials once, and your agent calls it. - **Permission scoping:** The location, menu, cart, and order ids sit in the URL path, so a rule can allow your agent to read menus and build carts while blocking order placement. You choose the operations it may call, so submitting an order is excluded unless you add it. - **Credential handling:** Your P&G Edge basic and bearer credentials are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'look up a menu' or 'place an order', and Jentic returns the matching P&G Edge operation with its input schema so the agent calls the right endpoint without reading the API docs. ## Related APIs - **Just Eat** — Food ordering and delivery marketplace API. - **Square** — Point-of-sale, catalog, and order APIs for merchants. - **Tebex** — Checkout and payments for digital goods and services. ## FAQ ### Is there a P&G Integration Edge MCP server? You don't need an MCP server to connect your agent to the P&G Integration Edge Service. Jentic connects it directly from the API Directory: import the API, store your credentials once, and your agent looks up menus and places orders on demand. ### Can I limit what my agent is allowed to do with the P&G Integration Edge Service? Yes. Write a rule that allows only the menu and cart operations, so the agent can build an order but cannot submit it. The location, cart, and order ids travel in the URL path, and every call the agent makes is logged. ### What authentication does the P&G Integration Edge Service use? Most calls authenticate with a bearer token, which you obtain by exchanging basic credentials at the token endpoint. Through Jentic both the basic and bearer credentials are stored once by your self-hosted instance and injected at call time, so they never reach the agent's context. ### Can I place an order with the P&G Integration Edge Service? Yes. Look up the location's menu, create a cart and update its items, then submit the order. The API returns the order so you can retrieve its details by id afterward. ### What are the rate limits for the P&G Integration Edge Service? The OpenAPI spec does not specify rate limits. Check the CompassDigital integration terms for current limits before running high-volume ordering traffic. ### How do I connect the P&G Integration Edge Service to my AI agent? Search the Jentic API Directory for the operation you need, such as placing an order, and import it. To run it on your own infrastructure, install Jentic One from its GitHub repo, then your agent calls the API with your credentials injected at execution time.