Machines & metering

Pairing a machine

1. POST /api/v1/nodes/pairings with { "listing_id": "LST-…" } returns a pairing code. Codes expire after 10 minutes; at most 5 open codes per listing.
2. The agent calls POST /api/v1/nodes/register. This route is public but must be signed by the key being registered and needs a live pairing code.
3. The agent sends POST /api/v1/nodes/{id}/heartbeat every 60 seconds, signed with the machine's key. Measurements arrive only in these signed requests and are never seller-typed.

Other routes: GET /nodes, GET /nodes/{id}, POST /nodes/{id}/edge-verdict (signed verdict from the edge verifier).

Whole GPUs and slices

	Whole GPU	Slice
What	A full physical device	Part of a device
Supported	NVIDIA, AMD	NVIDIA MIG only, from a known profile
Not supported	—	AMD compute/memory partitions that share the driver interface; self-certified slices

Overlapping device ranges are refused.

Metering

• Each heartbeat credits the gap between two heartbeats for every allocated device.
• Presence follows the allocated device id, not a device index.
• A health sensor the driver did not report counts as unknown, not healthy.
• Usage rolls up into hourly tranches; per-delivery slices are available at GET /deals/{id}/delivery/slices.