Anthropic AI

Use your own AI key and see what the account spends.

Connect an Anthropic key to the Netrix account that will use it. Netrix records calls by model and purpose, and every customer-facing output remains a suggestion or draft for a person to review.

Request access Explore the platform

FIELD NOTE / INTEGRATIONAnthropic AI

NETRIX

Evidence: 01
Decision: 02
Action: 03
Proof: 04

How the work moves

Observed100% Reviewed78% Applied52% Verified48%

Example statuses only. These numbers are not benchmarks or customer results.

What to look for

Get the answer without losing sight of where it came from.

Bring your own key

The encrypted credential belongs to the account and can be removed without showing its original value again.

Break usage down by feature

See whether tokens came from audit suggestions, review replies, or GBP content drafts.

Keep publishing with people

Claude prepares language; authorized people decide what to accept, deploy, or publish elsewhere.

What happens after you connect it

A working connection does not give every person—or every feature—permission to make changes.

NETRIXREVIEW / SCOPEAnthropic AI · authorized action

PROVIDER GATE

Identity
Capability
Permission

PUBLIC STATERead separatelyNo success inferred from a write response

This is a simplified example. Available actions and permissions depend on the provider, the connected account, and the change being requested.

From finding to follow-up

See where the work stands—and what still needs to happen.

01Found
Netrix records the page and the issue it found.
02Reviewed
Someone checks the finding in context.
03Approved
The right person chooses what should change.
04Applied
A supported connection accepts the change.
05Checked
Netrix reads the public page again.
06Shared
The report summarizes the audit and fixes currently marked applied.

A few things worth knowing

Netrix can prepare the work. Your team still makes the call.

01
Nothing publishes itself
AI drafts and supported SEO changes wait for an authorized person to act.
02
A write is not proof
Netrix records when a provider accepts a change, then checks the public page separately. If it cannot read the page, the result stays unknown.
03
Limits belong in the open
When a feature depends on another provider or stops short of a complete workflow, the page should say so.