For Agents
Register Hnry users, raise expenses, and manage invoices on behalf of self-employed contractors via the Hnry GraphQL Partner API.
Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Hnry Partner 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://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | shStep 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | 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.
What an agent can do with Hnry Partner API.
Register a new self-employed user into Hnry through the partner flow
Raise expense entries against a user's Hnry account for tax treatment
Create and manage invoices for a contractor's clients
GET STARTED
Use for: I want to register a new contractor in Hnry through our partner integration, Raise an expense against a contractor's Hnry account, Create an invoice for a contractor's client and return the invoice id, Retrieve the current invoice status for a contractor
Not supported: Does not handle payment collection, accounting general ledger, or non-AU/NZ tax filing — use for Hnry partner-driven contractor registration, expenses, and invoicing only.
Hnry is a financial admin platform for self-employed contractors and freelancers in Australia and New Zealand: it handles tax, invoicing, expenses, and statutory deductions automatically. The Partner API is a GraphQL endpoint that lets approved partners register users, raise expenses, and manage invoices on behalf of Hnry-customers. Authentication uses OAuth2 authorization code flow, so end users grant scoped consent before partner agents transact on their behalf.
Run any partner-permitted GraphQL query or mutation through a single endpoint
Use the OAuth2 authorization code flow to obtain scoped user consent
Patterns agents use Hnry Partner API for, with concrete tasks.
★ Partner-Driven Contractor Onboarding
Marketplaces and platforms that pay contractors register those contractors into Hnry so taxes and statutory deductions are handled automatically. The agent calls the Hnry registerUser mutation through the GraphQL endpoint after OAuth consent. Contractors avoid year-end tax stress and platforms reduce compliance friction.
Run the registerUser mutation against POST /graphql with the contractor's name, email, and platform reference id.
Automated Expense Capture
Bookkeeping or expense tools push expenses into Hnry on the contractor's behalf so deductions are applied to the correct income stream. The agent invokes the raiseExpense mutation against /graphql for each expense receipt or category. This means contractors keep accurate, real-time tax treatment without manual entry.
Invoke the raiseExpense mutation for user_456 with $120 categorised as 'Software Subscription' on today's date.
Invoicing for Contractor Clients
Platforms that handle work allocation also need invoicing on behalf of contractors. Hnry's GraphQL surface supports invoice creation and management, so an agent can mint invoices linked to platform-side jobs and read back their status. This avoids contractors maintaining a separate invoicing tool.
Run a createInvoice mutation for user_456 against client 'Acme' for $1,500 and return the new invoice id.
Agent-Run Contractor Operations
An AI ops agent connected via Jentic handles end-to-end contractor administration: register, raise expenses, mint invoices, and read state. OAuth2 tokens are stored in the Jentic vault and refreshed at execution time, so the agent never holds the raw access_token. End-to-end setup is under an hour because the agent loads the GraphQL operation on demand.
Onboard a new contractor into Hnry, raise their first expense from a receipt, and create their opening invoice for client 'Acme'.
1 endpoints — hnry is a financial admin platform for self-employed contractors and freelancers in australia and new zealand: it handles tax, invoicing, expenses, and statutory deductions automatically.
METHOD
PATH
DESCRIPTION
/graphql
Execute any GraphQL query or mutation
/graphql
Execute any GraphQL query or mutation
Three things that make agents converge on Jentic-routed access.
Credential isolation
Hnry OAuth2 tokens are stored encrypted in the Jentic vault. Agents request execution and Jentic refreshes and injects tokens at call time — the raw access_token never enters the agent context.
Intent-based discovery
Agents search by intent (e.g., 'register a contractor in hnry') and Jentic returns the GraphQL operation with the corresponding mutation schema, so the agent sends the right body without reading the GraphQL schema directly.
Time to first call
Direct Hnry integration: 2-3 days for OAuth2 wiring, GraphQL schema parsing, and partner mutation handling. Through Jentic: under 1 hour — search, load schema, execute.
Alternatives and complements available in the Jentic catalogue.
Stripe API
Stripe handles payment collection that flows into Hnry-managed contractor income
Choose Stripe to actually collect client payments; pair with Hnry to handle the tax and invoicing side for self-employed contractors.
Specific to using Hnry Partner API through Jentic.
What authentication does the Hnry Partner API use?
Hnry uses OAuth2 authorization code flow: end users grant consent and the partner receives scoped access tokens. Through Jentic, OAuth tokens are stored encrypted in the Jentic vault and refreshed at execution time, so the agent never holds the raw token.
Can I register users through the Hnry Partner API?
Yes. The Partner API exposes a registerUser-style mutation through POST /graphql so partners can onboard contractors after OAuth consent. The mutation typically returns the new user reference for use in subsequent expense and invoice operations.
Why does the Hnry API only show one endpoint?
Hnry is a GraphQL API: all queries and mutations are sent to the single POST /graphql endpoint, with the actual operation expressed in the request body. The OpenAPI spec captures this single entry point; the operation surface is described in the GraphQL schema itself.
How do I raise an expense for a contractor through Jentic?
Search Jentic for 'raise hnry expense', load the GraphQL POST operation, and execute with the raiseExpense mutation body containing user id, amount, and category. Use pip install jentic with the async SearchRequest, LoadRequest, ExecutionRequest pattern.
What countries does the Hnry API support?
Hnry primarily serves self-employed contractors in Australia and New Zealand, where the platform handles statutory deductions and tax filing. The Partner API is intended for platforms operating in those markets that need to wire contractor tax handling into their flow.