staffing & talent placement · NAICS 5613
The careers object an agent calls to get a placement
Placement records typed by O*NET-SOC — the G1 standard itself — each carrying a 90-day-validatable outcome. Keyless. Typed envelopes. The sandbox is the real product over clearly labeled example data.
- 5
- labeled example Placement records
- 4
- typed envelope outcomes
- 0
- keys required for first value
What answers today, keyless
Every claim below is a probe, not an adjective. The machine faces are generated from one manifest — docs cannot drift because docs render from it.
- agents.json — the capability card
- openapi.json — the 3.1 contract, live routes only
- [pricing — the rate card, rates[] keyed by operationId](/pricing)
- llms.txt — the markdown front door
- icp.json — agent classes and the B2A ladder
- verify — every claim as a runnable probe
- projection.json — this projection's G4 coordinates
curl https://api.careers/placements # typed OK envelope, labeled example data
curl https://api.careers/placements?status=completed # branch on the query
curl https://api.careers/placements?occupation=15-1252.00 # branch on the O*NET-SOC code
curl https://api.careers/placements/plc-952-0001 # one placement record by id
curl https://api.careers/pricing # the rate card (test mode; binding: false)One definition, every face
The quartet, the branching collection, and the 402 offer boundary are generated from the same frozen manifest.
O*NET-typed records
Every placement carries its O*NET-SOC code — the G1 standard itself is the type system, not a lookalike taxonomy.
The 90-day outcome grain
The placement record's product grain is a 90-day-validatable outcome: retained, pending, attrited, or converted — the seed shows all four.
One rate card, operation-keyed
rates[] keys on the same operationIds the contract declares — route = rate row, unified and fail-closed at the manifest.
Example data, labeled in-band
Every seed record says "example": true on the wire. The sandbox is the real product over simulated data — never a faked demo.
Settlement is not active on this deployment — the 402 offer boundary is served and typed, but no billing occurs. The pricing document states this on the wire (binding: false).
sandbox
Start with the anonymous floor
No key, no account, no conversation — the anon sandbox is the universal floor. Every seed record is synthetic example data, labeled in-band. O*NET-SOC codes on the records are the real standard's own (O*NET 29.0, U.S. Department of Labor, CC BY 4.0).