Install Jentic One Beta

Connect the Galaxy Unit API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Galaxy Unit 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%2Fgalaxyunit.app%2Fgalaxyunit" | 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%2Fgalaxyunit.app%2Fgalaxyunit" | 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 Galaxy Unit API.

Read a business summary of setup gaps, today's jobs, and unpaid invoices

Price services from the business price list with the estimate endpoint

List and create contacts, jobs, and quotes with idempotent writes

Create invoices and expenses and read them with their line items

Read revenue, spend by category, and unpaid invoices for a period

GET STARTED

Start building with Galaxy Unit API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Galaxy Unit API for, with concrete tasks.

★ AI Agent Business Assistant via Jentic

An AI agent reaches Galaxy Unit through Jentic to run a service business's day without wiring the bearer key itself. It searches by intent, receives the matching operation and its input schema, and executes the call with the key injected at run time. Because the key acts as its member under row-level security, the agent only ever sees what that member can see.

Search Jentic for 'what needs attention in my business today', load the GET /api/v1/business/summary schema, and execute it with the key injected at run time

Quote-to-Invoice Workflow

A service business prices a job, sends a quote, and bills the customer in one flow. Galaxy Unit prices the work from the business price list, creates a quote with line items, and then creates the invoice, each as an idempotent write. Writes can be previewed with a dry-run query parameter and may wait for an owner's approval before they commit.

Call POST /api/v1/estimate to price the work, POST /api/v1/quotes to create the quote, then POST /api/v1/invoices to bill the customer

Business Health Check

An owner or an agent checks how the business is doing at a glance. Galaxy Unit returns today's jobs, setup gaps, and unpaid invoices from the summary endpoint, and revenue and spend by category from the money endpoint. Money is returned as a decimal string so the agent reports figures without rounding errors.

Call GET /api/v1/business/summary for today's jobs and unpaid invoices, then GET /api/v1/business/money for revenue and spend over the period

Contact and Job Management

A service business adds a new customer and schedules work for them. Galaxy Unit creates the contact and then a job linked to the work, each write carrying an Idempotency-Key so a retried request is not duplicated. Updates send an If-Match version so a stale write is rejected instead of overwriting newer data.

Call POST /api/v1/contacts to add a customer, then POST /api/v1/jobs to create a job for them with an Idempotency-Key

Key Endpoints

23 endpoints — the galaxy unit api runs the customer and billing side of a service business for ai agents and scripts.

METHOD

PATH

DESCRIPTION

GET

/api/v1/me

Identity, member role, and business time zone

GET

/api/v1/business/summary

Setup gaps, today's jobs, and unpaid invoices

POST

/api/v1/estimate

Price services from the business price list

GET

/api/v1/contacts

List contacts

POST

/api/v1/jobs

Create a job

GET

/api/v1/invoices

List invoices

POST

/api/v1/invoices

Create an invoice

GET

/api/v1/business/money

Unpaid invoices, spend, and revenue for a period

GET

/api/v1/me

Identity, member role, and business time zone

GET

/api/v1/business/summary

Setup gaps, today's jobs, and unpaid invoices

POST

/api/v1/estimate

Price services from the business price list

GET

/api/v1/contacts

List contacts

POST

/api/v1/jobs

Create a job

GET

/api/v1/invoices

List invoices

POST

/api/v1/invoices

Create an invoice

GET

/api/v1/business/money

Unpaid invoices, spend, and revenue for a period

Why Jentic?

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

Setup

Wiring Galaxy Unit by hand means sending the bearer header with a gu_live_ key, setting an Idempotency-Key and If-Match version on every write, and handling the owner-approval step for pending writes yourself. Through Jentic you install once, import Galaxy Unit from the API Directory, store the key once, and your agent calls it.

Permission scoping

Galaxy Unit splits reads and writes: write operations need a write-scope key and can wait for owner approval, and every call runs as the member who created the key under row-level security. A rule can confine your agent to the read operations across contacts, jobs, and invoices, so it reports on the business without creating or changing records unless you allow it.

Credential isolation

Your Galaxy Unit key 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 'create a job for a customer' or 'read unpaid invoices', and Jentic returns the matching Galaxy Unit operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Galaxy Unit API through Jentic.

What authentication does the Galaxy Unit API use?

The Galaxy Unit API authenticates with a bearer token per its OpenAPI spec: you send an Authorization header carrying a gu_live_ key issued in Settings under Integrations by an owner or admin. The key acts as the member who created it under row-level security and never above admin. Through Jentic the key is stored encrypted by your own Jentic One instance and injected at execution time, so it never reaches the agent.

What are the rate limits for the Galaxy Unit API?

The OpenAPI spec does not specify rate limits. List endpoints use cursor pages and writes require an Idempotency-Key, which keeps a retried request from being duplicated under load. See https://galaxyunit.app/for-agents for current guidance.

Can I create invoices with the Galaxy Unit API?

Yes. POST /api/v1/invoices creates an invoice with a write-scope key and a required Idempotency-Key, and GET /api/v1/invoices/{id} returns it with its line items. You can preview a write first with the dry-run query parameter before it is committed.

Is there a Galaxy Unit MCP server?

You don't need an MCP server to give your agent Galaxy Unit. Jentic connects it directly from the API Directory: import it and your agent calls the contact, job, and invoice operations on demand, discovering each operation's schema when it needs it rather than loading a separate server's tool definitions into context.

How do I check my business summary with the Galaxy Unit API through Jentic?

Search Jentic for 'what needs attention in my business today', and it returns the Galaxy Unit summary operation with its input schema. Load it and execute GET /api/v1/business/summary with the key injected at run time. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Can I limit what my agent is allowed to do with the Galaxy Unit API?

Yes. Write a rule that allows only the read operations a task needs, for example listing jobs and reading unpaid invoices, so the agent can summarize the business but cannot create contacts, jobs, or invoices. Writes also respect the key's scope and can wait for an owner's approval, and every call runs through your own instance and is logged.

Galaxyunit App Galaxy Unit API

AI ReadinessAI-Aware (B-)61/100

See full scorecard

Official vendor OpenAPI document · agent-readyCRMContact Managementbearer23 EndpointsREST

For Agents

Manage a service business's contacts, jobs, quotes, invoices, and expenses, price work from the price list, and read a summary of jobs and unpaid invoices. All operations are secured with a bearer key that acts as its member under row-level security.

Use for: Get a summary of what needs attention in the business today, Create a job for a customer, List this month's unpaid invoices, Price a service from the business price list

Not supported: Does not handle payment capture, payroll, or email and SMS messaging. Use for managing a service business's contacts, jobs, quotes, invoices, and expenses only.

The Galaxy Unit API runs the customer and billing side of a service business for AI agents and scripts. It manages contacts, jobs, quotes, invoices, and expenses, prices work from the business price list, and returns a summary of setup gaps, today's jobs, and unpaid invoices. A money endpoint reports revenue, spend by category, and unpaid invoices for a period, and an activity log records every write. Keys act as the member who created them under row-level security, writes use an Idempotency-Key and can wait for owner approval, and money is returned as a decimal string in the business time zone.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

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.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: B-Signals: 4

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.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: D-Signals: 4

19%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

87%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

57%

Summary Coverage

Coverage of summaries across operations/tags/info.

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.

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).

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: CSignals: 1

54%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Galaxy Unit API to your agent

Capabilities

Start building with Galaxy Unit API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Galaxyunit App Galaxy Unit API

Jentic AI Readiness Score

Galaxy Unit API

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness