This guide gives you a small API you can use to test the full Lipafy loop: upstream service -> capability registration -> gateway call -> agent connection. The useful bit is flexible pricing: reading the menu can be free, while POST /order charges the total of the selected food items.
From the test app folder:
It listens on http://127.0.0.1:4010 and exposes:
Try it directly:
Create an API key in the local dashboard, then register the test capability against your local Lipafy API.
The price_amount is the fallback price. The private provider_config.lipafy_pricing policy below makes /menu and /health free, then charges POST /order by adding the item ids in the request body.
Local/private upstream URLs are allowed only outside production. In production, Lipafy blocks private addresses to prevent server-side request forgery. To test this against https://api.lipafy.xyz, deploy the hotel API somewhere public or expose it with a temporary HTTPS tunnel and use that public URL as provider_config.endpoint_url.
For your Netlify test deployment, use this endpoint instead:
List the menu through the gateway:
This call returns X-Payment-Charged: 0 because /menu is configured as a free browsing path.
Place a test order:
This order charges 1500 KES: 1200 for coastal-pilau plus 300 for passion-juice.
If you exposed the hotel API publicly and registered it on production, switch the base URL to https://api.lipafy.xyz:
After installing the CLI:
For Codex or another local MCP-capable client running on your machine, point it at your local Lipafy API:
For ChatGPT or any hosted MCP client, use the production URL and a publicly reachable hotel API endpoint:
Then ask the agent:
The agent should discover hotel.soko-garden.order and call lipafy.execute_capability.