APIs for the apps
your agents
need.
Find stores, read menus, and query service data through documented tools built on the APIs behind the apps.
Call a tool.
Get structured data.
Your agent asks for data. ajar calls the API behind the service and sends the result back. Here’s a store search, for example.
Your agent sends a location to the store search tool.
ajar handles the service’s request format and connection.
Store data comes back as JSON for your agent to use.
Speed
For supported operations, requests go straight to the service API. Skip the page loads, clicks, and screenshot processing.
Reliability
Your integration doesn’t depend on button positions, page layouts, or DOM selectors. It calls a documented operation and reads JSON.
Find your service.
See what’s supported.
Check the available tools, required inputs,
and connection status for each service.
Create a key.
Check its access.
Create a scoped key in your workspace. Use the identity endpoint to check its access before building your integration.
Read the authentication guidecurl "$AJAR_API_URL/v1/identity" \
-H "Authorization: Bearer $AJAR_API_KEY"Common questions.
What is ajar?
ajar wraps the APIs that services use in their own apps and exposes them as documented tools for agents and developers.
How is this different from browser automation?
ajar calls the APIs behind the apps directly. Your agent can move faster and use fewer tokens, without loading pages, clicking through menus, or interpreting screenshots.
Which services can I use?
Lots. See our supported sites.
Can I control what my agents can access?
Scope each API key to one service or your workspace. Set permissions, expiry, and request limits. Revoke it at any time.
Can I use ajar for personal projects?
Yes. Connect your own accounts and use ajar in your personal agents, scripts, and side projects. Start for $1 in your first month, then $15/month.
Can my team use ajar?
Yes. Enterprise accounts are invite only. Request access and tell us which services your team needs. We’ll reply within 3 hours.