FoundryNet / Error codes / HTTP / REST 402

HTTP / REST error code

402, Payment Required, billing, not permissions

The request is authenticated and permitted, but the account's billing state does not allow it. On Forge, 402 always means billing: never permissions.

Start free HTTP / REST → canonical

Diagnosis

When you hit this

A metered endpoint called on a plan that does not include it.
A quota exhausted for the period.
A lapsed payment method.

Resolution

How to fix it

Check plan entitlements
The endpoint may be premium on your tier. The pricing page is the source of truth for what is metered.
Inspect current usage
Query billing usage to see which meter is exhausted.

Normalization

What Forge does about it

402 and 403 mean different things on Forge and it is worth not conflating them: 402 is billing state, 403 is a guardrail. Retrying a 402 will not help until the billing condition changes.

Connect

Normalize HTTP / REST telemetry

One MCP endpoint serves every protocol adapter. 2,086 curated mappings, 985 canonical fields defined.

# normalize telemetry from HTTP / REST, one of 13 protocols Forge reads

claude mcp add --transport http forge https://mcp.foundrynet.io/mcp \

--header 'Authorization: Bearer YOUR_FORGE_KEY'

✓ forge connected, 32 tools available

Related

Keep reading

Other HTTP / REST codes: 401 403 422 429

Equipment that speaks HTTP / REST: Caterpillar Cummins Haas MiR (Mobile Industrial Robots) Universal Robots OTTO Motors 6 River Systems AGILOX Detroit Diesel Fetch Robotics

HTTP / REST protocol hub

Other protocols: Modbus OPC UA MQTT / Sparkplug B FANUC FOCAS EtherNet/IP PROFINET / S7 BACnet/IP J1939 (CAN) MTConnect ROS 2 (DDS) SNMP MAVLink CSV ingest

All error codes · All OEMs · All protocols

Why does a cross-vendor canonical data model matter? The Machine Agent breaks it down weekly. Read it →

Get the thesis behind this infrastructure: The Machine Agent, weekly.