Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Gateway REST 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%2Ftyk.com%2Ftyk" | shStep 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%2Ftyk.com%2Ftyk" | sh
jentic register # connects your agent to your Jentic One instanceJentic 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.
What an agent can do with Gateway REST API.
Access Gateway REST API resources via REST API
Manage developer tools data programmatically
Integrate Gateway REST API into automated workflows
Query and filter Gateway REST API records by parameters
Monitor Gateway REST API operational status and events
GET STARTED
Patterns agents use Gateway REST API for, with concrete tasks.
★ Developer Tools Operations
The API provides 18 endpoints for developer tools operations.
Execute a primary operation against the Gateway REST API
Data Retrieval and Monitoring
Query Gateway REST API resources on a schedule to track changes, generate alerts, or feed downstream dashboards. Agents poll relevant endpoints, compare against previous state, and trigger actions when thresholds are crossed.
Poll the primary Gateway REST API endpoint, compare response to last known state, and alert if changed
AI Agent Integration via Jentic
AI agents discover and call Gateway REST API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle none tokens manually.
Search Jentic for 'gateway rest API', load the operation schema, and execute with Jentic-managed credentials
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Tyk Gateway REST API by hand means resolving the gateway host for your deployment, matching each management operation to its request shape, and handling responses yourself. Through Jentic you install once, import the Gateway REST API from the API Directory, store the credential once, and your agent calls it.
Permission scoping
Scope your agent to the operations it needs from the Gateway REST API and nothing else. You choose the operations it may call, so management writes are not included unless you add them.
Credential isolation
Your Tyk gateway credential 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 'manage the API gateway', and Jentic returns the matching Gateway REST API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Alternatives and complements available in the Jentic catalogue.
Specific to using Gateway REST API through Jentic.
What authentication does the Gateway REST API use?
The Gateway REST API uses no authentication. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.
What are the rate limits for the Gateway REST API?
Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.
How do I use gateway rest API through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'use gateway rest API'. Jentic returns the matching Gateway REST API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the Gateway REST API have?
The Gateway REST API exposes 18 endpoints covering tyk operations.
Does the Gateway REST API support pagination?
Pagination support depends on the specific endpoint. Check the endpoint parameters for page, limit, or offset fields. Through Jentic, the operation schema exposes all available parameters so agents can paginate automatically.
Can I limit what my agent is allowed to do with the Gateway REST API?
Yes. Because you run Jentic One yourself, you decide which of the Gateway REST API operations your agent may call, and it can reach nothing else. You can grant only the read and query operations it needs while withholding management writes, so the agent never touches gateway configuration unless you explicitly add those operations. The stored Tyk gateway credential is injected at execution time and stays out of the agent's context, so scope is set by your rules rather than by the agent.
For Agents
Programmatically access Gateway REST API resources. Covers 18 operations.
Use for: I need to integrate with Gateway REST API, Find available developer tools operations, Get the current status of Gateway REST API resources, List all records from Gateway REST API
Not supported: Does not handle payments, communications, or crm - use for developer tools only.
tyk.com/main version 1.9. The API exposes 18 endpoints.