Share keys between the companies you run
Who this is for: An admin who runs more than one company on SpiderGate and wants them to use each other's provider keys instead of buying the same subscription twice.
What this does: Connects your companies so each one's requests can use the others' keys, lets you hold any key back with Keep private, and shows you which company used which key.
Before you begin
You are an admin of the company you are signed in as. Connecting is done by a person in the dashboard; an agent's token can read the group but cannot connect, pair or un-hide a key.
The other company is on SpiderGate too, and you either admin it as well or can reach its admin to swap a pairing code.
Each company has keys in its own vault. Sharing never copies a key: the other company can use it, never see it.
Steps
1. Open the connected-companies settings
Go to app.spideriq.ai/dashboard/gate/vault and open Settings. The Connected companies card lists every company you are connected to, how many keys each shares, your role and when you connected. If you are connected to nobody it reads "This company is not connected to another company."
2. Connect a company you also run
Click Connect a company. The dialog lists the companies where you are also an admin; click Select next to one. It shows how many keys that company shares. If one of them is a personal login, the dialog warns that vendor terms may forbid sharing it, and you tick the acknowledgement before you go on. Click Connect followed by the company's name. It appears in the table straight away.
3. Or pair with a company someone else runs
On your side, click Create pairing code and send the code to the other company's admin. A code works for 15 minutes. They open the same dialog, choose Pairing code, paste it, click Continue and then Request connection. They see "Code accepted. The other company's admin confirms next." You then see their request on your settings page: click Confirm to connect, or Decline. Click Cancel code to withdraw a code nobody has used.
4. Check the order your requests use keys in
The card Which keys a request tries, in order shows the order: this company's own keys first, then the keys of connected companies, then the public pool. The same order applies when a runner borrows a login.
5. Hold a key back with Keep private
Back in the vault, each of your keys has a Keep private switch. Turn it on and connected companies stop using that key; your own company keeps it. A key that already serves the public pool reads "already serves the public pool", and a key that can never be shared reads "never shared", so the switch is off for those.
6. Tell your agent to use it
Your agents use connected keys with no change: requests follow the order in step 4. To let an agent check the group and the keys it can use, install the gateway skill and ask it in plain words:
npx -y @spideriq/mcp-gate@latest"Read my SpiderGate group with gate_group, then list the subscriptions I can use with gate_subscriptions, and tell me which ones belong to a connected company."
The skill is @spideriq/gateway-skills. Over the API the same reads are GET /api/gate/v1/group and the connected array on GET /api/gate/v1/subscriptions; see the API reference.
Verify it worked
In the vault, filter the Owner column by the other company. Its shared keys appear in your list marked use only, with the owner, provider, plan, price and account email, and no Edit, Test, Revoke or Copy buttons. If you see them, the companies are connected.
Troubleshooting
The other company is not in the list when I click Connect a company? You are not an admin there, or it is already in another group (the dialog says so). Use a pairing code instead, or ask its admin.
The pairing code says "code not valid"? It was mistyped, cancelled, already used or expired. Create a new one.
A connected key I expected is missing? Its owner turned on Keep private, or the key is not a gateway key (only gateway keys can be shared).
My agent's token gets 403 when it tries to connect or turn Keep private off? That is intended. Those are a signed-in admin's acts; an agent may turn Keep private on, never off.