Take agentscore-py 2.7.0, fix the crypto intent parameter, release 2.12.0 - #147
Merged
Merged
Conversation
…_method_types, release 2.12.0 Stripe's 2026-09-30.preview API rejects payment_method_types on PaymentIntent create; allowed_payment_method_types is accepted there and on the 2026-03-04.preview merchants pin today (both checked in test mode). The SDK move drops get_reputation from the api re-export, since /v1/reputation was retired.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Dependency sweep and the reputation cleanup, released as 2.12.0.
agentscore-py>=2.7.0. The SDK droppedget_reputation()/aget_reputation()becauseGET /v1/reputationwas retired on 2026-09-30.agentscore_commerce.apire-exports the SDK'sAgentScoreclient, so those methods leave this package's surface too.The crypto deposit PaymentIntent is restricted with
allowed_payment_method_types: ["crypto"]instead ofpayment_method_types. Stripe's2026-09-30.previewAPI rejectspayment_method_typeson PaymentIntent create ("no longer supported"). I checked both fields in test mode with the same crypto deposit body:payment_method_typesallowed_payment_method_types2026-03-04.preview(what the storefronts pin)2026-09-30.previewThe GA
2026-09-30.endiverejects crypto deposit mode itself, so a merchant must keep pinning a preview version either way. A new test pins the field.Lock upgrades: stripe 16.0.0 (test and extra only; it pins
2026-09-30.endive, and the helper takes the merchant's own client), x402 2.25.0, cdp-sdk 1.48.2, cryptography 50.0.2, uvloop 0.23.0, ruff 0.16.10, python-dotenv 1.2.4, lefthook 2.1.16. x402 2.25.0 keeps Base USDC's EIP-712 name"USD Coin". Workflows move to uv 0.12.22.Docstrings and keywords:
apimodule comment no longer lists reputation.agentscore-pyis gone.trustandreputationkeywords are dropped, andagent-commercebecomesagentic-commerce.Type of change
Public API
AgentScore.get_reputation()andaget_reputation()disappear from theagentscore_commerce.apire-export, by way of agentscore-py 2.7.0. Migration: drop the call. The endpoint has returned 404 since it was retired, so this is versioned as a minor.create_multichain_payment_intentsends a different Stripe parameter with the same effect on the API versions merchants pin; its signature is unchanged.Test plan
test_create_multichain_payment_intent_restricts_to_crypto_with_allowed_typesasserts the parameter sent and thatpayment_method_typesis absent.uv run pytest(1887 passed, 4 skipped, 95.4% coverage),ruff check,ruff format --check,ty checkandvulturepass locally. The 41 warnings are pre-existing (the sanic and seamless-helper tests) and unchanged. The OSV scan ofuv.lockis clean.Worked with Varun.
Checklist