canonical: https://jentic.com/apis/galaxyunit.app/galaxyunit # Galaxyunit App Galaxy Unit API 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. ## For AI 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. ## Scope 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. ## Capabilities - 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 - Poll the activity log for writes and approvals since a timestamp - Check where a write awaiting owner approval stands ## Use cases ### 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. Example prompt: 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. Example prompt: 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. Example prompt: 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. Example prompt: 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 | 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 | ## Key resources - **Contacts and Jobs** — List, read, create, and update customers and jobs via `/api/v1/contacts` and `/api/v1/jobs` - **Quotes and Invoices** — Price, quote, and bill work via `/api/v1/estimate`, `/api/v1/quotes`, and `/api/v1/invoices` - **Expenses and Money** — Record expenses and read business analytics via `/api/v1/expenses` and `/api/v1/business/money` - **Account and Activity** — Read identity, the business summary, and the activity log via `/api/v1/me`, `/api/v1/business/summary`, and `/api/v1/events` ## AI readiness 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. - **Score:** 61 / 100 - **Maturity:** AI-Aware - **Dimensions:** - Foundational Compliance: 99 / 100 - Developer Experience & Jentic Compatibility: 63 / 100 - AI-Readiness & Agent Experience: 41 / 100 - Agent Usability: 94 / 100 - Security: 60 / 100 - AI Discoverability: 54 / 100 - **View full report:** https://jentic.com/apis/galaxyunit.app/galaxyunit/scorecard - **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/ - **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview ### Score it yourself Every API in the directory is allowlisted, so you can re-score it with no key required. - **Score your own API:** https://jentic.com/scorecard.md - **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md ```sh npx @jentic/api-scorecard-cli score ``` ## Why Jentic - **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 handling:** 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. - **Discovery method:** 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. ## Related APIs - **Xero Accounting** — Cloud accounting with invoices, bills, and expense tracking for small businesses - **Pipedrive** — Sales CRM for contacts, deals, and pipeline management - **Square** — Payment capture and point-of-sale for in-person and online charges ## FAQ ### 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.