Migration from FinChip
Replace obsolete FinChip terminology and flows with the current Finch product model.
FinChip has evolved into Finch. Existing FinChip material is useful historical context, but it must not be copied into current user documentation without verification.
Product changes
| Older FinChip documentation | Current Finch documentation |
|---|---|
| Skill-only marketplace | Three markets: Skills, Agents, and Tasks |
| “Token is API / Skill / Asset” as the main explanation | Start with the user outcome, then explain holdings, Call Rights, versions, and custody only where needed |
| Website, protocol, and generic CLI | Website + official Remote MCP + @finchtech/cli custody boundary |
fc_key Agent registration | Finch Personal Account, Remote MCP OAuth, and an active Finch CLI Session |
Agent autonomously calls legacy methods such as verify(fc_key) or getProtocol() | Agent client uses mounted first-class Finch Remote MCP tools; local signing remains in the CLI |
| Choose ERC-1155 License Mode or ERC-721 Fork Mode in the publisher UI | Current V3 Skill form does not expose a token-standard choice; document source, content mode, price, supply, version, and exact chain instead |
| Every Skill is encrypted | Skills can be Public or Protected; protected modes include Finch-managed and Lit where available |
| Skill files are uploaded “to the blockchain” | Packaging, storage delivery, content protection, chain records, and wallet transactions are separate layers |
| Secondary trading and reselling as a primary workflow | Do not promise a secondary market unless a current live surface and contract are verified |
| Closed-beta points and invitation tiers | Treat as legacy unless a current Dashboard campaign explicitly exposes them |
| legacy merchant API keys | Finch does not issue legacy merchant API keys; current Chat Agent runtime uses versioned credential setup and mutual signing |
| One generic Agent mode | Chat Agent supports Conversation, Task, and Generation Offers; Direct API is a separate P4 contract |
| “Buy a Skill” and “call an API” are closely conflated | Skill holdings deliver packages; Agent Call Rights authorize hosted executions |
Current naming
Use these terms in public copy:
- Finch, not FinChip, for the product and ecosystem.
- Personal Account, not just wallet account.
- Listing Center, not Studio, for the current owner workspace.
- Chat Agent for the user-facing connection model.
- Finch Agent protocol v2 for new runtime integrations.
- Legacy signed protocol only when documenting compatibility.
- Direct API for the separate synchronous typed contract.
- Call Rights, not generic API credits or tokens.
- Skill package and protected delivery, not “encrypted file on-chain.”
- Task Market Task when it could be confused with an Agent's asynchronous Task Offer.
What can carry forward
These principles remain useful when rewritten for the current product:
- AI capabilities should be discoverable and reusable.
- Creators need clear distribution, pricing, versioning, and support boundaries.
- Wallet ownership can authorize market actions and protected delivery.
- Users should review descriptions, instructions, limitations, cost, and provenance before acquiring.
- Agents can discover and use market capabilities through a machine-readable interface.
Migration checklist for existing pages
- Replace every old product name and URL.
- Remove
fc_key,getProtocol(), generic FinChip CLI, and old command examples. - Remove unverified ERC-721 Fork, resale, refund, royalty, audit, and governance promises.
- Separate Skill, Agent, and Task journeys.
- Add Personal Account, Dashboard, Settings, Listing Center, Tasks Center, and Run History.
- Add Chat Agent and Direct API as distinct Provider and buyer flows.
- Add Remote MCP/CLI identity and custody boundaries.
- Add explicit public-versus-protected Skill delivery.
- Add version, Offer, Call Rights, Artifact, operation, and recovery concepts.
- Re-test every live route before publication.
Legacy support
The current Listing Center can display previous-generation Skills and mark some as delivery unavailable. The Chat Agent publisher can select Legacy signed protocol for an existing compatible runtime. Legacy does not mean the old documentation is still authoritative; follow the migration and compatibility behavior shown by the current Finch surface.
An original legacy API key may still be accepted only through Finch's migrated-account login flow. It is not a current Finch CLI, Remote MCP, or Provider credential. Follow Migrate to Finch for account access, asset claims, and merchant balance migration.