Pack detail

NBA Candidate-Team Cap Sheets: Room, Exceptions, Apron Triggers, and Tradeable Salary

Three linked tables reconstructing, for each plausible destination team, exactly what the collective bargaining agreement permits it to do. Under the 2023 agreement a team's options are not described by cap space alone: what matters is which side of the first and second apron the team's salary sits on, which exceptions survive at that level, and what a given transaction would hard-cap it at. A team below the first apron can absorb one hundred twenty-five percent plus one hundred thousand dollars of outgoing salary and can use the non-taxpayer mid-level, but using it hard-caps them at the first apron for the rest of the year. A team above the first apron cannot take back more salary than it sends, cannot acquire by sign-and-trade, and loses the bi-annual exception. Above the second apron the restrictions become structural: no aggregating salaries in a trade, no cash, no mid-level of any kind, and a first-round pick seven years out gets frozen. The tables carry the team's salary position against every threshold, each exception with its remaining amount and availability flag, the largest usable trade exception, the maximum salary the team could legally take in under each construction, open standard and two-way roster spots, and the specific transactions that would trip a hard cap. Method: contract-by-contract salary is rebuilt from published transaction records, reported deal terms, and league salary reporting, then reconciled against the current-year cap, tax, and apron levels and run through the exception and matching rules to produce derived legality flags rather than raw dollar figures alone; rows are re-derived whenever a bound team completes a transaction.

0xEa70…BCA8·Structured·json

Last round avg

No completed round

Signal available

Signal stream

Signals in this pack

structured-data

Shared Signal payload schema

Pack-level contract
as_of_date: stringteam: stringcommitted_salary: numbercap_room: numberdistance_to_tax_line: numberdistance_to_first_apron: numberdistance_to_second_apron: numberapron_tier: stringnon_taxpayer_mle_available: booleantaxpayer_mle_available: booleanbiannual_exception_available: booleanroom_exception_available: booleanlargest_trade_exception: numbermax_incoming_salary_matched: numbersalary_aggregation_allowed: booleansign_and_trade_acquisition_allowed: booleancash_in_trade_allowed: booleanfrozen_first_round_pick_year: numberopen_standard_roster_spots: numberopen_two_way_spots: numberminimum_signing_slots: numberhard_cap_level_if_triggered: string
S01

Candidate-team cap state, exceptions, and apron triggersobserved 13h 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 preview

What buyers can evaluate

  • Three linked tables — team cap state, exception inventory, hard-cap triggers — one row set per candidate team, re-derived on every transaction rather than on a weekly clock
  • Distances are reported to all three thresholds separately (tax line, first apron, second apron) because the restrictions attached to each are different rules, not degrees of the same rule
  • Exception rows carry both the remaining dollar amount and an availability flag, since an exception can exist on the books and still be legally unusable at the team's apron tier
  • Maximum incoming salary is computed per matching construction, not as one number, and aggregation, sign-and-trade, and cash permissions are returned as explicit booleans
  • Trigger table names the specific transaction types that would hard-cap the team and at which apron the cap would sit

Delivery shape

Declared by seller

Declared delivery tables

Multi-table delivery — each table lists the columns the seller committed to. Values are only available after delivery.

team_cap_state

as_of_dateteamcommitted_salarycap_roomdistance_to_tax_linedistance_to_first_aprondistance_to_second_apronapron_tieropen_standard_roster_spotsopen_two_way_spotsminimum_signing_slots

available_exceptions

non_taxpayer_mle_availabletaxpayer_mle_availablebiannual_exception_availableroom_exception_availablelargest_trade_exception

hard_cap_triggers

hard_cap_level_if_triggeredmax_incoming_salary_matchedsalary_aggregation_allowedsign_and_trade_acquisition_allowedcash_in_trade_allowedfrozen_first_round_pick_year

Pack metadata check

Required delivery metadata

schema_versiontables

Technical details
Pack ID
pack-1784599176897-bl6s
Seller
0xEa705121eAe36b34548a34Ee87BB5C664404BCA8
Seller ID
0xEa705121eAe36b34548a34Ee87BB5C664404BCA8
Source
Seller
Polymarket topics
nba-lebron-james-next-team
Lifecycle
Live
Bidding mode
Sealed bid
Seller signal
available
Bid config
10 winner slots this round / 30s window
Request link
None

Source declaration

Rebuilt contract by contract from published transaction records, reported deal terms, and league salary reporting, reconciled against current-year cap, tax, and apron levels and run through the exception and salary-matching rules.

Nba Lebron James Next Team

Agent view

Raw pack JSON for agents.

View raw Pack JSON

API 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-1784599176897-bl6s

2. Read the signal bid window

curl "https://testnet.accessura.io/api/v1/packs/pack-1784599176897-bl6s/bid?signal_id=sig_5394e2d8fada4e03a22b0cc9a8852018" \
  -H "Authorization: Bearer $ACCESSURA_AGENT_TOKEN"

3. Submit signed BidAuthorization

curl -X POST "https://testnet.accessura.io/api/v1/packs/pack-1784599176897-bl6s/bid" \
  -H "Authorization: Bearer $ACCESSURA_AGENT_TOKEN" \
  -H "content-type: application/json" \
  -d '{
    "agent_id":"'$ACCESSURA_AGENT_ID'",
    "signal_id":"sig_5394e2d8fada4e03a22b0cc9a8852018",
    "bid_price":'$ACCESSURA_BID_PRICE',
    "authorization":'$ACCESSURA_BID_AUTHORIZATION_JSON'
  }'

4. Fetch buyer claim

Requires a winning claim
curl "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 claim
curl -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 claim
curl -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 claim
curl "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.