ONELY_BUDGET_PER_CALL and ONELY_BUDGET_DAILY sit next to the wallet key in the configuration, which makes the agent's exposure a setting rather than a matter of restraint. The buying loop closes properly too: 1ly_call returns purchase metadata carrying a purchaseId and a reviewToken, and 1ly_review requires both, so a review is tied to a purchase that actually settled. Worth knowing before you install it: the surface covers two quite different jobs, buying and reselling APIs on one hand and launching, trading and claiming fees on Bags.fm tokens on the other, and the token tools are marked Bags-only rather than being a general trading interface.
An agent commerce client for 1ly.store: buying paid APIs with automatic x402 payment on one side, running your own store — links, keys, stats, payouts — on the other, plus a set of Bags.fm token tools.
- The buying side: 1ly_search across the marketplace filtered by type and price range, 1ly_get_details for one endpoint's pricing, reviews and payment info, 1ly_call, which settles payment over x402 automatically and returns the response with purchase metadata, and 1ly_review, which uses the purchaseId and reviewToken from that metadata.
- The selling side: 1ly_create_store from a wallet signature returning a store and an API key, 1ly_create_link for a paid or free API link with a price, slug, visibility and webhook, plus 1ly_update_link, 1ly_delete_link, 1ly_list_links and 1ly_get_stats per store or link.
- Store administration: 1ly_list_keys, 1ly_create_key and 1ly_revoke_key, with 1ly_update_profile, 1ly_update_socials and 1ly_update_avatar.
- Payouts: 1ly_withdraw to a named Solana wallet address, and 1ly_list_withdrawals for the requests already made.
- Bags.fm token tools: 1ly_launch_token handling metadata, fee configuration, the launch transaction, signing and submission, 1ly_list_tokens by creator wallet, 1ly_claim_fees for a token's fee share, and 1ly_trade_token with 1ly_trade_quote for a quote that executes nothing.
ONELY_WALLET_SOLANA_KEY, the Solana wallet payments settle from, with ONELY_BUDGET_PER_CALL and ONELY_BUDGET_DAILY bounding what it may spend. An ONELY_API_KEY for the store-side tools: link management, keys, stats, withdrawals and profile updates each state that they require it. A wallet signature to create the store in the first place.
One command — npx @1ly/mcp-server
