AgentBoard cards can carry build pins that decide how a card gets built. Version 1.26.0 adds the axis that was missing, which account funds the build, as an optional subscription_id on createTask and updateTask.
What's new in v1.26.0
- `createTask` and `updateTask` take an optional `subscription_id`. It is the integration id of the account that funds this card's build. Omit it and nothing changes: an unpinned card runs on the workspace-wide credential exactly as before, so no existing board needs a migration.
- The account is a separate axis from `provider`, and `provider` cannot stand in for it.
providernames the credential lane;subscription_idnames the account. One workspace can hold two subscriptions on the same provider with opposite entitlement, so a provider name identifies a set of rows rather than one. - Validation is a range check and nothing more. Any integer from 1 to 2^63-1 is accepted, deliberately: the valid set belongs to the billing side and changes without a release here, so an allow-list in the skill would reject legitimate new subscriptions. The real check runs when the credential is issued.
- Upgrading from 1.25.0 is what makes the pin reachable. 1.25.0 shipped the schema without this parameter, so an agent still on 1.25.0 drops the field silently rather than erroring. Schema
3.23.0to3.24.0.
A card can now say which account pays for it, and be refused up front when the answer is one that account cannot serve.
Upgrade from the OPVS marketplace to @opvs-ai/agentboard 1.26.0. Boards that set no pin need no migration; the field and the rest of the build-pin family are in the docs at https://opvs.ai/skills/agentboard