feat: add paymentMethods array to service registry#554
Merged
brendanjryan merged 5 commits intomainfrom Apr 13, 2026
Merged
Conversation
Co-authored-by: Matthew <83676602+dev-slater@users.noreply.github.com> Amp-Thread-ID: https://ampcode.com/threads/T-019d86ac-6a5d-707a-bfdf-3f1af417e1d3
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Thanks for submitting a service to the MPP directory! If you want your service included in the curated Required
Recommended
Review criteriaWe prioritize services that are high quality and novel. We may not approve services that duplicate existing functionality or aren't yet production-ready. |
…te methods with intents
Instead of a flat paymentMethods: string[] that duplicates info without
carrying intents or assets, use payments: PaymentDefaults[] on ServiceDef.
This lets buildService() generate the methods object with intents and
assets co-located per method — matching the discovery spec's x-payment-info
structure where method is always paired with intent.
Multi-method services (Browserbase, Alchemy, PostalForm, Stripe Climate,
Papercut) now produce:
methods: {
tempo: { intents: ['charge'], assets: ['0x20c0...'] },
stripe: { intents: ['charge'], assets: ['usd'] }
}
No new schema fields needed — the existing methods object handles it.
Collaborator
|
made several changes to this which make it more correct -- ok to merge now |
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
3 participants
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.
Adds a
paymentMethodsfield to every service entry in the registry. This exposes which payment protocols each service accepts (for example["tempo", "stripe"]) so the directory UI and agents can surface supported payment methods per service.Motivation
Services like Browserbase, Alchemy, Stripe Climate, PostalForm, and Papercut accept both Tempo stablecoins and Stripe card payments, but the registry had no way to express this — every service only declared a single
paymentdefault.Changes
schemas/services.ts— addedPaymentMethodIdtype and requiredpaymentMethodsarray onServiceDef. Populated for all 88 services based on live 402/openapi.json probes:["tempo", "stripe"](Browserbase, Alchemy, PostalForm, Stripe Climate, Papercut)["tempo"]scripts/generate-discovery.ts— emitspaymentMethodsin the generateddiscovery.jsonschemas/discovery.schema.json— addedpaymentMethodsto the schemasrc/data/registry.ts— addedpaymentMethodsto the client-sideServicetypescripts/generate-discovery.test.ts— updated test fixturesTesting
Prompted by: Matthew