Proposal: read-only AssetFare multichain quote action provider

Open
#1,500 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
30/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
openapi, typescript
Domain
api, backend-api-design

Research direction

Start by reviewing the standalone provider and its four isolated Jest tests in the linked AssetFare repository, then compare them with current AgentKit provider patterns and the repository contribution guide. Confirm the proposed read-only scope and maintainer acceptance before adapting it to the monorepo; done means the provider and tests pass the stated Prettier, ESLint, TypeScript, and Jest checks.

Written by the indexing model from the issue text.

Description

Proposal

Would the AgentKit maintainers accept a read-only AssetFare action provider?

AssetFare exposes a capped REST/OpenAPI v2 route service for nine asset
endpoints and 72 directed conversions across Solana, Base, Arbitrum, and
Robinhood Chain. The proposed provider would add only two actions:

  • assetfare_get_capabilities
  • assetfare_quote_route

The provider would not accept a private key or expose authentication, session
creation, action preparation, signing, submission, funding, swap, or bridge
execution. It would require agents to compare every fresh quote against other
executable routes and would fail closed unless AssetFare reports server signing
and submission as disabled.

Why it may fit AgentKit

  • AgentKit supports EVM and SVM wallet environments while the quote intent
    carries its own source and destination chains.
  • No AssetFare API key or wallet is required for the first read-only call.
  • The integration gives an agent a neutral route candidate without granting
    AssetFare custody or transaction authority.
  • Execution remains outside this provider and requires explicit caller approval
    and caller-controlled wallets.

Existing implementation and verification

A standalone provider and tests are available here:

https://github.com/odaiin/assetfare-mcp/tree/main/integrations/coinbase-agentkit

The proposed upstream version is adapted to the current AgentKit monorepo and
passes:

  • Prettier format check
  • ESLint
  • TypeScript check
  • four isolated Jest tests

Public contracts:

If a built-in provider is in scope, I have a patch and changeset ready and can
open a signed PR following the repository contribution guide. If maintainers
prefer this to remain an external provider, I will keep it in the AssetFare
repository instead.

Dominant language
TypeScript
Stars
1.3k
Forks
822
Avg merge
13h 31m
Merged PRs (30d)
2

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from coinbase/agentkit

All issues in coinbase/agentkit

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.