CoeusX
CoeusX
CoeusX
CoeusX
LAWG APIFor developers & product teams

Build tax research
into your product.

Give your users access to Lawg’s Australian tax research. Bring questions, documents and source-backed answers into the workflows you build.

Request API access Explore capabilities
Server-to-server access. Credentials issued by CoeusX.
WHAT YOU CAN BUILD

Research capabilities.
Your product experience.

Build a research assistant, add a document question-and-answer step, or bring cited analysis into your existing software.

Research questions

Bring Australian tax research into an assistant, a client workflow or an internal tool.

Document context

Let users ask questions grounded in the supported documents they provide.

Follow-up questions

Continue from a completed response, building on the earlier facts within the context limits.

Sources for review

Return structured citations alongside available answers so practitioners can inspect their basis.

START BUILDING

From a question
to a retrievable result.

Integrate through your backend using a focused HTTP API. Keep your interface, customer relationships and business logic.

  1. 01

    Arrange access.

    Receive your organisation credential, integration guide and agreed limits from CoeusX.

  2. 02

    Submit your request.

    Send a question with optional ready file IDs. Save the returned response ID.

  3. 03

    Bring the result into your product.

    Check progress, retrieve the available answer and present its citations for professional review.

Request exampleHTTP / JSON
POST/v1/responses
POST /v1/responsesAuthorization: Bearer <YOUR_API_KEY>Idempotency-Key: <NEW_OPERATION_KEY>Content-Type: application/json {  "model": "lawg",  "input": "What facts should I gather to assess GST registration for an Australian business?",  "stream": false}

Submit a question. Save the returned response ID to retrieve its status and result.

Illustrative request outline · no live API call
THE INTERFACE

The essentials,
in a few endpoints.

Add documents, ask questions and manage responses. Retrieve the same operation after a connection drops, without starting another research task.

01

Add context

Upload a supported document, then reference its ready file ID in a research request.

POST/v1/files
02

Ask and follow up

Submit a question with optional files. Continue the discussion using a previous response ID.

POST/v1/responses
03

Retrieve the result

Read the operation status and available final answer, with structured citations for source review.

GET/v1/responses/{id}
04

Request cancellation

Cancel work that is no longer needed, then read the response to confirm its state.

POST/v1/responses/{id}/cancel

The integration guide covers request fields, supported inputs, limits and error handling. It is provided with your approved access.

ACCESS & RESPONSIBILITY

Clear boundaries.
From the first request.

Organisation credentials define access to Lawg resources. Your backend authorises the people and matters within your application.

Keep credentials on your server.

Call over HTTPS with a Bearer credential. Keep keys out of frontend code, client logs and shared documents.

Separate organisations.

Lawg enforces the assigned organisation boundary. Your application controls which users can access each customer, matter and resource ID.

Agree the operating scope.

Set usage limits and data requirements with our team during onboarding. Support is available through support@coeusx.ai.

BEFORE YOU BUILD

A few practical
questions.

Planning an integration?
Talk to our team

How do we get API access?

Contact CoeusX with your product, intended workflow and expected usage. Access is arranged with our team. We provide the integration guide, assigned endpoint, organisation credentials and agreed limits during onboarding.

Does each end user need a Lawg account?

Your backend calls Lawg using an organisation credential. You manage your own users and authorise access to their customers, matters, files and response IDs. Keep API keys on your server; do not embed them in browsers or mobile apps.

Can we use documents and ask follow-up questions?

Yes. Upload a supported file, wait for it to be ready, and include its file ID in a question. Use a completed response ID for a follow-up. Supported formats, size limits and context limits are specified in your integration guide.

What if a request or connection is interrupted?

If you have the response ID, retrieve that operation with GET. If a submission has an uncertain outcome, retry the same request with the same idempotency key within the documented recovery window. Use bounded retries; a timeout does not prove the operation was rejected.

Are answers ready to send directly to clients?

Answers are research outputs for professional review. Citations help practitioners inspect sources; they do not certify the analysis. Review the facts, assumptions and applicable authority before relying on an answer or sharing it with a client.

How are pricing and usage limits set?

Pricing, permitted use and capacity are agreed during onboarding. Contact our team to discuss your workload and deployment needs.

BUILD WITH LAWG

Bring tax research
into your next workflow.

Tell us what you’re building. We’ll work through access, integration requirements and the right scope together.

Request API access Already integrating? Contact supportRead our privacy policy