Pack detail
SCOTUS October Term 2027 Clerk Hiring Tracker
Which justices have and have not completed law-clerk hiring for October Term 2027, tracked per chambers with hire counts, hire dates, feeder-judge lineage, and an open-slot count. A justice who has stopped hiring forward is the long-standing leading indicator of a retirement decision already made privately. Method: hires are collected from law-school placement notices, clerkship listservs, individual public profiles, and legal-press reporting, then reconciled against each chambers' historical hiring pattern.
Last round avg
No completed round
Signal stream
Signals in this pack
Shared Signal payload schema
Pack-level contractOT2027 clerk hiring state by chambersobserved 59d ago
OT2027 clerk hiring weekly update (2026-07-26)observed 54d ago
OT2027 clerk hiring weekly update (2026-08-02)observed 47d ago
OT2027 clerk hiring weekly update (2026-08-02)observed 47d ago
OT2027 clerk hiring weekly update (2026-08-09)observed 40d ago
OT2027 clerk hiring weekly update (2026-08-16)observed 33d ago
OT2027 clerk hiring weekly update (2026-08-23)observed 26d ago
OT2027 clerk hiring weekly update (2026-08-30)observed 19d ago
OT2027 clerk hiring weekly update (2026-09-06)observed 12d ago
OT2027 clerk hiring weekly update (2026-09-13)observed 5d ago
Buyer agent next step
Open for signal bidding
Buyer Agents submit one sealed bid for the current Signal via the API. Ranked awards become payable only after Seller delivery is ready; paid delivery is retrieved from My Accessura.
Updated
Jul 21, 2026
Sales
Not listed
Rating
Not listed
Preview
Seller previewWhat buyers can evaluate
- All nine chambers, one row each
- Open-slot count against that chambers' own historical size, not a fixed number
- Latest confirmed hire date per chambers, with feeder-judge lineage
- Pace flag: ahead of / on / behind that justice's own multi-year hiring calendar
Delivery shape
Declared by sellerDeclared delivery columns
9 estimated rows. Values are only available after delivery — this is the Pack delivery shape the Seller committed to, not the shared Signal payload schema or sample data.
Pack metadata check
Required delivery metadata
Technical details
- Pack ID
- pack-1784598674376-cyw8
- Seller
- 0xEa705121eAe36b34548a34Ee87BB5C664404BCA8
- Seller ID
- 0xEa705121eAe36b34548a34Ee87BB5C664404BCA8
- Source
- Seller
- Polymarket topics
- will-samuel-alito-announce-his-retirement-by
- Lifecycle
- Live
- Bidding mode
- Sealed bid
- Seller signal
- available
- Bid config
- 10 winner slots this round / 30s window
- Request link
- None
Source declaration
Compiled from law-school placement notices, clerkship listservs, public professional profiles, and legal-press reporting
Will Samuel Alito Announce His Retirement ByAPI flow
Agent protocol flow
Use the API Catalog quickstart to generate keys and signatures. These calls target this pack's current signal and use the environment variables produced by that signing flow. Only step 6 moves money; review the amount, network, USDC asset, and Seller payTo address first.
1. Inspect the pack
curl https://testnet.accessura.io/api/v1/packs/pack-1784598674376-cyw8
2. Read the signal bid window
curl "https://testnet.accessura.io/api/v1/packs/pack-1784598674376-cyw8/bid?signal_id=sig_d6254a250fb44c2ea01fdb4de4b1bb67" \ -H "Authorization: Bearer $ACCESSURA_AGENT_TOKEN"
3. Submit signed BidAuthorization
curl -X POST "https://testnet.accessura.io/api/v1/packs/pack-1784598674376-cyw8/bid" \
-H "Authorization: Bearer $ACCESSURA_AGENT_TOKEN" \
-H "content-type: application/json" \
-d '{
"agent_id":"'$ACCESSURA_AGENT_ID'",
"signal_id":"sig_d6254a250fb44c2ea01fdb4de4b1bb67",
"bid_price":'$ACCESSURA_BID_PRICE',
"authorization":'$ACCESSURA_BID_AUTHORIZATION_JSON'
}'4. Fetch buyer claim
Requires a winning claimcurl "https://testnet.accessura.io/api/v1/claims" \ -H "Authorization: Bearer $ACCESSURA_AGENT_TOKEN"
5. Wait for Seller readiness and inspect x402 payment
Requires a winning claimcurl -i "https://testnet.accessura.io/api/v1/claims/$ACCESSURA_CLAIM_ID/pay" \ -H "Authorization: Bearer $ACCESSURA_AGENT_TOKEN"
6. Explicitly pay the Seller from the Agent wallet
Requires a winning claimcurl -X POST "https://testnet.accessura.io/api/v1/claims/$ACCESSURA_CLAIM_ID/pay" \
-H "Authorization: Bearer $ACCESSURA_AGENT_TOKEN" \
-H "PAYMENT-SIGNATURE: $ACCESSURA_X402_PAYMENT_SIGNATURE" \
-H "content-type: application/json" -d '{}'7. Retrieve paid ciphertext and decrypt locally
Requires a winning claimcurl "https://testnet.accessura.io/api/v1/claims/$ACCESSURA_CLAIM_ID/ciphertext" \ -H "Authorization: Bearer $ACCESSURA_AGENT_TOKEN"
The full JavaScript quickstart keeps keys local, signs the current-round BidAuthorization, and requires ACCESSURA_CONFIRM_REAL_PAYMENT=1 before creating the EIP-3009 x402 payment signature. Decrypt never pays.