Install Jentic One Beta

Connect the Estimate Rocket API V1 to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Estimate Rocket API V1, 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%2Festimaterocket.com%2Festimaterocket" | sh

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%2Festimaterocket.com%2Festimaterocket" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic 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 Estimate Rocket API V1 API.

List and retrieve clients, projects, proposals, assignments, invoices, and payments

Create new clients and projects when a job is won

Record a payment against an invoice via the payments endpoint

Subscribe to and unsubscribe from webhooks for downstream automation

Identify the current authenticated employee with the /me endpoint

GET STARTED

Start building with Estimate Rocket API V1 API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Estimate Rocket API V1 API for, with concrete tasks.

★ Daily operations dashboard for a painting contractor

A back-office dashboard pulls today's assignments via /api/v1/assignments and joins them against /api/v1/projects and /api/v1/clients so the office manager sees crew, job, and customer in one view. Outstanding invoices come from /api/v1/invoices and pending payments from /api/v1/payments. The integration is read-heavy and refreshes every few minutes during the work day.

GET /api/v1/assignments, then for each one GET /api/v1/projects/{id} and /api/v1/clients/{id} to assemble today's crew schedule with customer details.

Sync invoices and payments to an external accounting system

Finance keeps QuickBooks or Xero aligned with Estimate Rocket by listing /api/v1/invoices and /api/v1/payments on a schedule and writing each new record to the accounting system. To avoid polling, they subscribe to webhooks via /api/v1/webhook_subscriptions so a fresh invoice or payment fires an event in near real time.

POST a webhook subscription to /api/v1/webhook_subscriptions for the invoice.created event, then on each callback GET /api/v1/invoices/{id} and create the matching invoice in the accounting system.

Lead-to-client conversion when a proposal is accepted

When a proposal is accepted, the CRM or website tool POSTs a new client to /api/v1/clients and a new project to /api/v1/projects so the contractor's office can dispatch crews and prepare the first invoice. Proposal IDs from /api/v1/proposals link the new project back to the winning quote for audit and reporting.

POST a new client to /api/v1/clients with the homeowner's details, then POST a project to /api/v1/projects referencing the accepted proposalId returned by /api/v1/proposals.

AI agent answering 'what jobs do we have today?' from a chat tool

An AI agent in the contractor's team chat answers questions like 'what jobs do we have today?' by searching Jentic for the right Estimate Rocket operation, calling /api/v1/assignments, and summarising the result with the linked project and client. Through Jentic, the OAuth token is held in the vault and only a scoped execution token is exposed to the agent.

Search Jentic for 'list contractor assignments today', execute GET /api/v1/assignments, then summarise the count and crew/site for each entry into a chat message.

Key Endpoints

19 endpoints — jentic publishes the only available openapi specification for estimate rocket api v1, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/api/v1/clients

List clients

POST

/api/v1/clients

Create a client

GET

/api/v1/projects

List projects

POST

/api/v1/projects

Create a project

GET

/api/v1/invoices

List invoices

POST

/api/v1/payments

Record a payment

POST

/api/v1/webhook_subscriptions

Subscribe to a webhook event

GET

/api/v1/clients

List clients

POST

/api/v1/clients

Create a client

GET

/api/v1/projects

List projects

POST

/api/v1/projects

Create a project

GET

/api/v1/invoices

List invoices

POST

/api/v1/payments

Record a payment

POST

/api/v1/webhook_subscriptions

Subscribe to a webhook event

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring Estimate Rocket by hand means running its OAuth2 flow, refreshing tokens, and shaping client, project, invoice, payment, and webhook payloads yourself. Through Jentic you install once, import the Estimate Rocket API from the API Directory, store the OAuth credentials once, and your agent calls it.

Permission scoping

The listed Estimate Rocket operations act on collections such as clients, projects, invoices, and payments, so scope the agent to the operations it needs, such as listing clients or reading invoices. You choose which operations are allowed, so a write like creating a payment is not included unless you add it.

Credential isolation

Your Estimate Rocket OAuth tokens are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'list clients' or 'create a project', and Jentic returns the matching Estimate Rocket operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Estimate Rocket API V1 API through Jentic.

Why is there no official OpenAPI spec for Estimate Rocket API V1?

Estimate Rocket does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Estimate Rocket API V1 via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

What authentication does the Estimate Rocket API use?

The API uses OAuth 2.0; clients exchange credentials at POST /login for an access token that is then sent on subsequent requests. Through Jentic the OAuth token is held in the vault and the agent receives only a scoped execution token, so the raw access token never enters the agent's context.

Can I record a payment with the Estimate Rocket API?

Yes - POST /api/v1/payments creates a payment record (typically against an invoice). Use GET /api/v1/payments/{id} afterwards to confirm the persisted values and GET /api/v1/invoices/{id} to verify the invoice's outstanding balance is updated.

What are the rate limits for the Estimate Rocket API?

The Estimate Rocket spec does not publish a numeric rate-limit policy. Treat list endpoints (assignments, invoices, projects, payments) as paginated and avoid tight loops; back off on any 429 or 5xx response.

How do I subscribe to invoice events through Jentic?

Search Jentic for 'subscribe to a webhook in Estimate Rocket'. Jentic returns POST /api/v1/webhook_subscriptions with the event-name schema. Execute it with the desired event (for example, invoice.created) and your callback URL; new invoices then trigger your endpoint without polling.

Which user is identified on each call?

GET /api/v1/me returns the currently authenticated employee record so an integration can scope its UI or filter results to that employee. The token's owner controls what records the API can read or modify.

Can I limit what my agent is allowed to do with the Estimate Rocket API?

Yes. Because you run Jentic One yourself, your own rules decide which Estimate Rocket operations and stored OAuth credentials the agent may use. The listed operations act on collections such as clients, projects, invoices, and payments, so you can allow read-only calls like listing clients or reading invoices and leave write actions out. A write such as creating a payment via POST /api/v1/payments or subscribing to a webhook is not available to the agent unless you add it.

Estimate Rocket API V1

Name: Estimate Rocket API V1 API
Brand: Estimate Rocket API V1
Availability: InStock

Agent-ready OpenAPI document · curated by JenticFinanceAccountingoauth219 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Read clients, projects, proposals, invoices, and payments from Estimate Rocket and subscribe to webhooks so contractor workflows stay in sync.

Use for: I need to create a new client in Estimate Rocket after a sales call, List all open projects so a dispatcher can assign crews, Retrieve an invoice by ID to email it to a homeowner, Record a payment against an invoice when a check clears

Not supported: Does not handle estimating math, GPS routing, or payroll - use for reading and writing Estimate Rocket clients, projects, proposals, invoices, payments, and webhook subscriptions only.

Jentic publishes the only available OpenAPI specification for Estimate Rocket API V1, keeping it validated and agent-ready. Estimate Rocket is a job-management and estimating platform built for painting and small construction contractors. Its API exposes the records that contractors care about every day - clients, projects, proposals, assignments, invoices, and payments - together with webhook subscriptions for keeping a back-office system in sync. OAuth2 controls access and a /me endpoint identifies the current employee on each request.

Jentic One on Github View OpenAPI Document

Connect the Estimate Rocket API V1 to your agent

Capabilities

Start building with Estimate Rocket API V1 API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Estimate Rocket API V1