Official vendor OpenAPI document · agent-readyDeveloper ToolsMonitoring Observabilitybearer38 EndpointsREST
For Agents
Configure Heroku dyno autoscaling rules, manage organizations and applications, and set up alert recipients for HireFire-managed scaling events.
Use for: I want to set up autoscaling for my Heroku web dynos, List all applications connected to my HireFire organization, Create a new manager rule that scales workers based on queue depth, Retrieve the current memberships in a specific organization
Not supported: Does not handle deployments, log aggregation, or APM metrics - use for Heroku dyno autoscaling configuration only.
HireFire automates dyno scaling for Heroku applications based on web request queue time and worker job metrics. The API exposes management of organizations, accounts, applications, managers (autoscaling rules), recipients (alert targets), and time ranges so platform teams can configure when and how dynos scale up or down. It supports memberships and users for team-based access to scaling policies across multiple Heroku accounts.
Install Jentic One Beta
Connect the HireFire API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the HireFire 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%2Fhirefire.io%2Fhirefire" | 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%2Fhirefire.io%2Fhirefire" | 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 HireFire API.
Configure web and worker autoscaling managers for Heroku applications with custom thresholds
Add and remove Heroku accounts, applications, and team memberships under a HireFire organization
Create alert recipients to receive notifications when scaling events trigger or thresholds breach
Schedule active time ranges that gate when autoscaling rules are allowed to fire
Audit organization users, memberships, and per-application manager configuration
Use Cases
Patterns agents use HireFire API for, with concrete tasks.
★ Heroku Web Dyno Autoscaling
Platform engineers connect Heroku applications to HireFire and create manager rules that scale web dynos up or down based on request queue time. The API lets agents register the application, attach a manager with target metrics, and confirm the manager is active before traffic events. Setup typically takes minutes per app once the Heroku account is linked.
Create a HireFire manager for application id app_123 with web dyno scaling between 1 and 10 dynos and verify the manager is enabled.
Worker Queue Autoscaling
Background-job heavy services use HireFire to scale Sidekiq, Resque, or custom worker dynos based on job queue length. The API exposes worker-type managers separately from web managers so different queues can scale independently. This avoids over-provisioning idle workers and reduces Heroku spend on bursty workloads.
List all worker-type managers attached to application id app_456 and update the maximum dyno count to 20.
Scaling Alerts and Recipients
Operations teams need notification when scaling events occur or when an application hits its dyno ceiling. HireFire recipients let teams attach email destinations to organizations so on-call engineers see scaling activity in real time. The API supports listing, adding, and removing recipients without touching Heroku itself.
Add ops@example.com as a recipient on organization org_789 and confirm the recipient appears in the recipients list.
Agent-Driven Heroku Cost Control
An AI agent connected via Jentic monitors Heroku spend and dyno utilization, then adjusts HireFire manager thresholds when traffic patterns shift. The agent loads HireFire operations on demand, updates min/max dyno settings, and confirms changes through the API. Credentials stay in your Jentic One instance so the agent never holds the bearer token directly.
Reduce the maximum dyno count on application id app_999 from 15 to 8 during a low-traffic time range and verify the update succeeded.
Key Endpoints
38 endpoints — hirefire automates dyno scaling for heroku applications based on web request queue time and worker job metrics.
METHOD
PATH
DESCRIPTION
GET
/organizations
List organizations
GET
/organizations/{id}/users
List users in an organization
POST
/memberships
Create a membership
GET
/organizations/{id}/memberships
List memberships in an organization
GET
/organizations
List organizations
GET
/organizations/{id}/users
List users in an organization
POST
/memberships
Create a membership
GET
/organizations/{id}/memberships
List memberships in an organization
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.
H
HireFire API
- AI-Aware (B)67/100
99
Foundational Compliance63
Developer Experience & Jentic Compatibility51
AI-Readiness & Agent Experience94
Agent Usability60
Security62
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
99
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: A+Signals: 4
97%
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).
100%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
63
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: B-Signals: 4
0%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
50%
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.
51
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: C-Signals: 4
38%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
100%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
66%
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).
62
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: B-Signals: 1
62%
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 HireFire API by hand means managing a bearer token for the Authorization header and walking its nested organization, membership, and application resources. Through Jentic you install once, import the HireFire API from the API Directory, store the token once, and your agent calls it.
Permission scoping
HireFire puts the organization id in the URL path (/organizations/{id}/users, /organizations/{id}/memberships), so a rule can pin your agent to one organization and the operations around it. You choose the operations it may call, so destructive ones like deleting an organization or an application are not included unless you add them.
Credential isolation
Your HireFire bearer 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 'configure Heroku dyno autoscaling', and Jentic returns the matching HireFire operation with its input schema so the agent calls the right endpoint without reading the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using HireFire API through Jentic.
What authentication does the HireFire API use?
The HireFire API uses bearer token authentication. The API key is passed as a Bearer token in the Authorization header on every request. Through Jentic, the bearer token is stored encrypted in your Jentic One instance and injected at execution time so agents never see the raw key.
Can I configure worker dyno autoscaling with the HireFire API?
Yes. The HireFire API exposes manager resources that attach to either web or worker dyno types on a Heroku application. POST a manager with the worker dyno name and your min/max dyno bounds to scale background-job processes independently from web dynos.
What are the rate limits for the HireFire API?
HireFire does not publish hard rate limits in its OpenAPI spec, but recommends staying below a few requests per second per organization. If you hit limiting, the API returns 429 responses; back off and retry. For agent workloads through Jentic, batch reads via GET /organizations/{id}/applications rather than polling individual managers.
How do I create a manager for a Heroku app through Jentic?
Search Jentic for 'configure heroku autoscaling manager', load the POST /organizations operation chain, then call the manager creation endpoint with the application id and dyno bounds. Run pip install jentic and use SearchRequest, LoadRequest, ExecutionRequest from the async client to wire this up in under an hour.
Does the HireFire API support time-based scaling rules?
Yes. The API exposes time range resources that gate when managers are allowed to fire. You can create overlapping time ranges (for example, weekday business hours versus weekend) and attach different scaling thresholds to each, all through CRUD operations on the time range endpoints.
Can I limit what my agent is allowed to do with the HireFire API?
Yes. Jentic One is self-hosted, so your own rules decide which HireFire operations and credentials the agent may use. Because HireFire puts the organization id in the URL path, such as /organizations/{id}/users and /organizations/{id}/memberships, you can pin the agent to a single organization and the operations around it. You also choose the exact operations it may call, so destructive ones like deleting an organization or an application stay out of reach unless you add them.
GET STARTED