fortrabbit API
66
AI ReadinessAI-Aware (B)66/100
Official vendor OpenAPI document · agent-readyCloud InfrastructureComputebearer26 EndpointsREST
For Agents
List and create apps, provision and restart environments, trigger deployments, and read deployment logs. Manage custom domains, and view the payment methods, people, and teams on the account.
Use for: I want to create a new app on fortrabbit, List all apps on my account, Deploy the latest code to an environment, Read the deployment logs for a deployment
Not supported: Does not provide databases, DNS hosting, or CDN configuration. Use for managing fortrabbit apps, environments, deployments, and custom domains only.
The fortrabbit API manages application hosting on the fortrabbit platform: it lists and creates apps, provisions and restarts environments, triggers deployments, and reads deployment logs. It manages the custom domains attached to apps and exposes the payment methods, people, and teams on the account. Apps and environments can be created, updated, restarted, and deleted through their resource collections.
Install Jentic One Beta
Connect the fortrabbit API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the fortrabbit 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.
1
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%2Ffortrabbit.com%2Ffortrabbit" | sh2
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%2Ffortrabbit.com%2Ffortrabbit" | 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.
Capabilities
What an agent can do with fortrabbit API.
List and create hosting apps and update or delete an individual app
Create, update, restart, and delete environments for an app
Trigger a deployment for an environment and read its deployment logs
List and remove the custom domains attached to an app
List and remove the payment methods on the account
List the people and teams associated with the account
Use Cases
Patterns agents use fortrabbit API for, with concrete tasks.
★ Agent-Managed Deployments
An AI agent connected through Jentic can create an app, provision its environment, trigger a deployment, and then read the deployment logs to confirm success, without a developer wiring the fortrabbit API by hand. The agent discovers each operation by intent and calls it with a stored token.
Create an app, provision an environment, trigger a deployment, and read the deployment logs
Custom Domain Setup
Teams point their own domains at a hosted app. fortrabbit lists the domains on an app and manages the domain records, so a new domain can be attached and an old one removed as part of a release.
List the domains on an app and attach a new custom domain to it
Account and Billing Review
Operators audit who can access an account and how it is billed. fortrabbit lists the people and teams on the account and the payment methods attached to it, so an agent can report membership and billing state.
List the teams and people on the account and report the attached payment methods
Key Endpoints
26 endpoints — the fortrabbit api manages application hosting on the fortrabbit platform: it lists and creates apps, provisions and restarts environments, triggers deployments, and reads deployment logs.
METHOD
PATH
DESCRIPTION
GET
/v1/apps
List apps
POST
/v1/apps
Create an app
POST
/v1/environments/{publicId}/deployments
Create a deployment for an environment
GET
/v1/deployments/{publicId}/logs
Get deployment logs
GET
/v1/domains
List domains
POST
/v1/environments
Create an environment
POST
/v1/environments/{publicId}/restart
Restart an environment
GET
/v1/apps
List apps
POST
/v1/apps
Create an app
POST
/v1/environments/{publicId}/deployments
Create a deployment for an environment
GET
/v1/deployments/{publicId}/logs
Get deployment logs
GET
/v1/domains
List domains
POST
/v1/environments
Create an environment
POST
/v1/environments/{publicId}/restart
Restart an environment
Jentic AI Readiness Score
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
F
fortrabbit API
- AI-Aware (B)66/100
89
Foundational Compliance62
Developer Experience & Jentic Compatibility50
AI-Readiness & Agent Experience94
Agent Usability60
Security66
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.2
Show dimension breakdown
89
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: ASignals: 4
98%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
100%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
60%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
62
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: B-Signals: 4
4%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
43%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
100%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
50
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: D+Signals: 4
37%
Description Coverage
Coverage of descriptions across API elements.
73%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
31%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
59%
Summary Coverage
Coverage of summaries across operations/tags/info.
94
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: A+Signals: 1
94%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
60
Security
Trust, risk posture, and security compliance.
Grade: B-Signals: 1
60%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
66
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: BSignals: 1
66%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the fortrabbit API by hand means managing its bearer token, sequencing environment and deployment creation, and polling deployment logs yourself. Through Jentic you install once, import fortrabbit from the API Directory, store the token once, and your agent calls it.
Permission scoping
fortrabbit carries the app id in the URL path (/v1/apps/{publicId}), so a rule can pin your agent to one app and the operations you pick, such as creating deployments and reading logs. You choose the operations it may call, so destructive ones like deleting an app, an environment, or a domain are not included unless you add them.
Credential isolation
Your fortrabbit token 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 'deploy an app' or 'read deployment logs', and Jentic returns the matching fortrabbit operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using fortrabbit API through Jentic.
What authentication does the fortrabbit API use?
The fortrabbit API authenticates with a personal API token sent as a bearer token in the Authorization header, per its OpenAPI spec. Through Jentic the token is stored encrypted by your own Jentic One instance and injected at call time, so it never reaches the agent's context.
Can I trigger a deployment with the fortrabbit API?
Yes. You create a deployment on an environment and then read its deployment logs, so an agent can ship a release and confirm the outcome from the log output.
Can I limit what my agent is allowed to do with the fortrabbit API?
Yes. Because the app id sits in the URL path, write a rule that pins the agent to one app and allows only the deployment and log-reading operations, so it can ship and inspect releases without deleting apps, environments, or domains. Every call it makes is logged.
Is there a fortrabbit MCP server?
You do not need an MCP server to give your agent the fortrabbit API. Jentic connects it directly from the API Directory: import fortrabbit, store your token once, and the agent calls its operations by intent without loading another server's tool definitions into its context.
What are the rate limits for the fortrabbit API?
The OpenAPI spec does not specify numeric rate limits for the fortrabbit API. Check the fortrabbit documentation at https://fortrabbit.com for current limits.
How do I deploy an app with the fortrabbit API through Jentic?
Search Jentic for an intent like 'deploy an app', and it returns fortrabbit's deployment-creation operation with its input schema so your agent can trigger a deployment and read its logs. To run it on your own infrastructure, install Jentic One from its GitHub repo.
GET STARTED