Neo.Tax Help Center

Connect AI agents with the public API and MCP server

Let your AI agents and scripts read, and optionally update, your Neo.Tax data with an API key, and see how access is controlled.

Neo.Tax has a public API and a hosted MCP server, so AI agents (Claude Code, Cursor, the Claude API, or your own scripts) can work with your Neo.Tax data without a browser. An agent connects with an API key that belongs to you, and sees exactly what you see in the app.

This article covers turning the API on, creating a key, connecting an agent, and how access is controlled. It is written so you can forward it to your security team.

Turn on the public API for your organization

The public API is off until an organization admin turns it on.

We’re rolling the public API out gradually, so it may not appear in your Organization settings yet. To have it enabled for your organization, email support@neo.tax.

  1. Open Organization settings.
  2. Turn on the public API.

While it is off, no member can create a key, and no existing key works. Turning it off takes effect on every member’s next request, without revoking keys one by one.

Create your API key

  1. Open your personal settings and find the API key section.
  2. Choose how long the key should last, up to one year.
  3. Choose whether the key may change data. Keys are read-only unless you allow writes.
  4. Create the key and copy it. The full key is shown only once. Neo.Tax stores only a hash of it, so it cannot be shown again.

You can hold one key at a time. To replace a key, revoke it and create a new one. Your settings page shows your key’s prefix, when it was created, when it expires, whether it may write, and when it was last used.

Connect an agent

After you create a key, the settings page shows everything you need:

  • The MCP URL, for MCP clients such as Claude Code and Cursor
  • The REST base URL, for scripts and tools such as curl
  • Ready-to-paste configuration for Claude Code and Cursor, and a sample curl request

Paste the configuration into your client and replace the placeholder with your key. The agent can then list your companies and work from there.

What an agent can read

A key can run only a fixed, documented set of operations, not arbitrary queries. Between them they cover:

  • Every product: your companies and fiscal years, a company’s profile and connected providers, the questionnaire and its answers, organization members, and background jobs that are still running
  • R&D tax credit: the credit estimate, R&D projects with their determinations and tickets, payroll qualified research expenses (QREs) and their summary, and generated documents with their statuses
  • Software capitalization: reporting periods, projects with their capitalization status and dates, each project’s tickets and why they were matched to it, project team members, wages and their capitalized share, and summaries. Every software capitalization request names the reporting period, so an agent never quotes a figure for a period it picked on its own.

Money is returned in cents. Lists return at most 100 rows per request, with a cursor for the next page.

What an agent can change

Only a key created with write access can change data, and only through these operations:

  • Update an R&D project’s details and narrative fields
  • Set one employee’s R&D project allocations for a fiscal year
  • Move tickets into an R&D project
  • Update a software capitalization project’s details and capitalization dates
  • Set one contributor’s project allocations for a reporting period
  • Move tickets into a software capitalization project

Moving tickets works the same as moving them between projects in the app: allocations follow the tickets, and the response shows each affected project’s new ticket count. An R&D move skips tickets outside the project’s fiscal year.

A write is allowed only when you could make the same change in the app, and is refused for the same reasons. For example, changes to locked periods and to fiscal years whose Form 6765 has been sent are refused. Every change appears in the record’s history as made by you through the public API.

MCP clients are told which tools only read and which change data, so clients such as Claude can ask before an agent runs a write. A read-only key is offered only the read tools.

How access is controlled

  • A key acts as its owner. It sees exactly the companies and data its owner can see in the app, including your company’s PII redaction. It never grants more access than its owner has.
  • Read-only by default. A key can change data only if its owner allowed writes when creating it.
  • Keys expire. Every key expires within one year.
  • Keys can be revoked at any time. You can revoke your own key, and organization admins can see and revoke any member’s key from the Members page. Revocation takes effect immediately.
  • Admins cannot create keys for others. Every key is held by the person who created it.
  • The organization switch. Turning the public API off stops every key in your organization on its next request.
  • IP allowlists apply. If your organization restricts access to certain IP addresses, keys are held to the same restriction.
  • Keys are separate from SSO. If your organization requires login through SAML or OIDC, that requirement applies to signing in to the web app, not to API keys. A key keeps working until it expires, its owner or an admin revokes it, its owner is removed from your organization in Neo.Tax, or an admin turns the public API off. Disabling someone only in your identity provider does not stop their key, so remove them in Neo.Tax as well.
  • Rate limits. Each key can make 60 requests a minute. Beyond that, requests are refused with a message saying how long to wait.
  • Request history. Neo.Tax records each request made with a key (who, which operation, and when) and keeps the record for 90 days.

FAQs

Can I see which of my members have API keys?

Yes. Organization admins see each member’s key on the Members page, with its prefix, creation date, expiry, last use, and whether it may write.

What happens to a member’s key when they leave?

Removing them from your organization revokes their key automatically, and it stops working immediately. You don’t need to revoke it separately.

I lost my key. Can I see it again?

No. Neo.Tax never stores the full key. Revoke it and create a new one.

Does the API cost extra?

No. The public API and MCP server are included at no extra cost.

Esc
↑ ↓ to move Enter to open