Overview

Some things should happen without you, others go faster with an assistant. Your inventory system writes a change note into the blog, your build server publishes a release note — or you ask Claude which scenes of a screenplay still have no location. Both work with personal keys.

Two kinds of keys

What a key may do

Every key works in exactly one account. What it may do there is the intersection of three things:

• what you yourself may do in that account,
• what you chose when creating the key,
• and what the account's administration has opened to AI assistants and programs.

A key can therefore never do more than you. If your role in the account changes, your key follows within five minutes at the latest.

First: the account opens the connection

Keys come with every paid package. On top of that everything starts shut in the account: under Settings → Personal keys the owner opens

• whether outside AI assistants are allowed, up to which level (read only, or also propose drafts) and in which areas (story & screenplay, production and media come chosen — people, finance and websites & blog stay out until the owner adds them on purpose),
• whether programs are allowed and whether they may also write.

On the same page the administration sees every member's keys with their last use and can revoke any of them at once.

Creating a key

Under My profile → AI & integrations there are two ways, depending on who gets the key:

The dialog then asks for:

1. the account the key is to work in, if you work in several. What you cannot choose, it explains to you — for example that the administration has not opened the connection yet;
2. a name that later tells what the key was for — "Claude on my laptop", "Release bot";
3. for an assistant the AI level and the areas, for a program the tasks it may do. Optionally you limit a program to certain address ranges;
4. Create key — ModiFax shows you the key, the matching address and a ready first call.

How a call identifies itself

The key travels in the Authorization header as Bearer and always starts with modi_pat_:

Authorization: Bearer modi_pat_a1b2c3d4e5f6_…

The account is never part of the call, it comes from the key. GET /v1/me tells you which account and which tasks your key works with.

Revoking

When a system is switched off or a key has fallen into the wrong hands, tap Revoke at the key and confirm. Within seconds every call with it is refused. The key stays in the list as Revoked, so it remains traceable that it existed.

Protocol

At the key, Protocol opens everything it called in the last 90 days: which task, how often and with which outcome — Done, Throttled (too many calls), Refused or Failed. Contents never appear there. The administration sees the same protocol for every key of the account under Settings → Personal keys.

Taking back what a program created

If a program created records, the protocol also offers Take back what it created. You choose a period, confirm, and ModiFax deletes every record the key newly created in it — through the normal delete, with your rights and in the protocol. What the program only changed stays.

Automatic suspension

If a key keeps breaking its limits within a short time — say because a program is stuck in a loop — ModiFax suspends it automatically. Every further call is then refused, and you and the administration get a notification and an email. In the list the key shows as Suspended with the reason. Only the administration can lift it, by hand under Settings → Personal keys → Unsuspend — once it is clear what happened.

Limits

• 120 calls per minute per key for reading, 30 for writing, 1,500 per account over all keys.
• An AI assistant proposes at most 30 draft packages per hour, with up to 500 drafts each.
• Writing tasks also have an hourly and a daily quota per account.
• Above that you get 429 with Retry-After — wait briefly and retry. Whoever keeps ignoring it is suspended automatically.
• Every call is recorded: key, task, outcome and time, never the contents.