SkillAgentSearch skills...

lienfi

Research and buy tokenized US tax lien certificates on LienFi (Base, USDC) — screen the live book by NET yield with no credential, then, once your operator has authorized your wallet in a browser, register and run the prepare → sign → confirm → submit → report purchase loop from the wallet you contr…

Install / Use

npx skills add BankrBot/skills --skill lienfi

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

93/100

Supported Platforms

Zed

Our assessment of lienfi

lienfi scores 93/100 on our quality scale, 88th of 421 Education & Research skills we index (top 21%).

Its SKILL.md is 21 KB long, well organised into 17 sections with 10 code examples: a thorough specification that gives an agent plenty to work with.

With 1,201 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
30/30
Structure
20/20
Description
15/15
Adoption
13/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated about 2 months ago, so lienfi is actively maintained.
  • Our last check on 2026-10-26 found the source still online.
  • No license is declared. By default that means all rights are reserved: you can read it, but reusing or redistributing it is not clearly permitted. Ask the author before building on it commercially.
  • Its trust signals score 88/100, with 1 caution from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-10-07. Automated pattern scan on 2026-10-07. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

lienfi compared with similar skills

All 4 of these similar skills score higher than lienfi; compare them before choosing.

SkillScoreStarsUpdatedFormat
lienfi (this skill)by BankrBot931.2k54d agoSKILL.md
Agent-Reachby Panniantong100112.3k8d agoCLAUDE.md
rufloby ruvnet10081.9ktodayCLAUDE.md
headroomby headroomlabs-ai10079.8ktodayCLAUDE.md
last30days-skillby mvanhorn10068.0ktodayCLAUDE.md

Frequently asked questions

How do I install lienfi?
Run npx skills add BankrBot/skills --skill lienfi. The install tabs above show the steps for each supported agent.
Which AI agents does lienfi work with?
It is written for Zed, as a SKILL.md file. Other agents that read the same format can often use it too.
Is lienfi safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It declares no license and scores 88/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is lienfi still maintained?
The repository was last updated about 2 months ago, so lienfi is actively maintained.

name: lienfi description: Research and buy tokenized US tax lien certificates on LienFi (Base, USDC) — screen the live book by NET yield with no credential, then, once your operator has authorized your wallet in a browser, register and run the prepare → sign → confirm → submit → report purchase loop from the wallet you control. LienFi signs only the price; every transaction leaves your wallet. emoji: 🏛️ tags: [lienfi, tax-liens, real-estate, base, usdc, mcp, investing] visibility: public

LienFi Skill

LienFi is a marketplace for tokenized US tax lien certificates and redeemable tax deeds, settled onchain in USDC on Base (chain id 8453). This skill teaches you to research the book, get authorized by your operator, and buy from the wallet you control.

Three facts before anything else:

  • LienFi never holds your key and never submits a transaction for you. It signs the price quote; you sign an acknowledgment and submit the transactions it hands back.
  • Purchases are final. A lien you buy belongs to your operator. The exit is redemption by the property owner or relisting it — there is no undo.
  • One human step exists, and it cannot be skipped or retried around. Your operator signs an authorization in a browser at https://app.lienfi.com/agents/authorize and hands you what that page prints. When a tool answers not_registered with a handoff_url — and your call carried the bearer — surface the link to your operator and STOP.

Prerequisites

Your wallet

Two ways to hold a Bankr wallet, and every step below works either way:

  • You are Bankr's own agent (the terminal, X or Telegram). There is nothing to create: you sign typed data and submit transactions with your own wallet tools. Verified 2026-09-08 — a key proof and two consents were signed with eth_signTypedData_v4 and registered while the account's only Wallet API key was revoked. Wherever a step shows a curl to api.bankr.bot, do the same thing with your wallet tool instead.
  • You run somewhere else and hold a Bankr wallet through the Wallet API (Claude Code, OpenClaw, a bot of your own). Create a key at https://bankr.bot/api-keys and keep it as BANKR_API_KEY. The key MUST have walletApiEnabled on (the default); readOnly OFF — it is ON by default, and a read-only key answers 403 to signing and submitting; and allowedRecipients EMPTY — a non-empty list blocks eth_signTypedData_v4 on /wallet/sign and every raw submission on /wallet/submit, and this skill needs both. Use allowedIps for restriction instead.

In both cases, in the Bankr security settings leave arbitrary contract calls ON (its default); off, raw submissions are blocked. Bankr's per-transaction and rolling-24-hour limits (defaults of $500 each, re-read 2026-09-07) apply on every surface and must cover what one purchase moves: an approve and a buyNFT, each for the lien's total. Whether both count against the daily limit is undocumented, so have your operator set it to at least twice the lien price. Only your operator can change these, in the Bankr web app. On X, Bankr answers only Bankr Club members.

Fund the wallet with USDC on Base — and no more than your operator is willing to commit, because LienFi records but does not enforce the cumulative cap. Gas on Base is sponsored for Bankr embedded wallets.

Your wallet address

Inside Bankr, it is the wallet your portfolio shows. Over the Wallet API:

curl -s https://api.bankr.bot/wallet/me -H "X-API-Key: $BANKR_API_KEY"

The address that holds the funds is the one your operator must name as the agent wallet. Give it to them exactly as returned. Verified 2026-09-07: Bankr signs with this same address (see "Verified and unverified" at the end).

Endpoints

  • LienFi MCP — JSON-RPC 2.0 over stateless HTTP, nothing to install, no session: POST https://api.lienfi.com/api/v1/mcp with content-type: application/json. Every LienFi call in this skill is one curl to it. Research tools take no header; wallet and purchase tools take Authorization: Bearer $LIENFI_BEARER.
  • Research REST, no credential — https://api.lienfi.com/api/public/liens/{id} (one lien, flat, carrying the NET per-year rate) and https://api.lienfi.com/api/v1/liens?... (the book with filters).
  • Read before your first call — https://app.lienfi.com/llms.txt (the money conventions), https://app.lienfi.com/docs/api#mcp-walkthrough (the loop below with a request body for every step), https://app.lienfi.com/docs/api#mcp-refusals (every refusal code with what to do). Trust tools/list over any document, including this one.

Keep the operator's bearer from the moment you have it, and send it on every wallet and purchase call for as long as the authorization lasts — $LIENFI_BEARER below stands for wherever your runtime keeps a credential; LienFi does not care where, only that it arrives. Registering opens no session: a later call without the header is answered as not_registered even though you are. Never print the bearer and never send it anywhere but api.lienfi.com. (Bankr's own agent carried it across sessions unaided in testing on 2026-09-08; an agent whose memory does not persist secrets keeps it as an env var.)

Money rules that are not guessable from the field names

  • Every yield LienFi's API returns is gross. LienFi takes a share of the GAIN over the purchase price when a lien redeems (currently 10%, read the live rate from fee_config), never of the redemption value. Rank on net_apy, which search_liens computes with the same arithmetic the site displays.
  • A buyer pays listing_price. Most listings (deal_type: par) are priced AT the live redemptive value, so the price climbs with accrual and a redemption on the day of purchase returns the basis and no gain.
  • Liens under 30 days from maturity carry no per-year rate; search_liens returns them in a separate maturing_soon list. Do not annualize them yourself.
  • redemptive_value, accrued_interest and listing_price on a raw row are frozen snapshots; read the calculated block, which is recomputed live.
  • redemption_deadline is the statutory deadline and is immutable onchain. Never recompute it.

Step 1 — Research (no credential)

List what the server serves, then screen:

MCP=https://api.lienfi.com/api/v1/mcp
curl -s -X POST $MCP -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

curl -s -X POST $MCP -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","id":2,"method":"tools/call",
       "params":{"name":"market_overview","arguments":{}}}'

curl -s -X POST $MCP -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","id":3,"method":"tools/call",
       "params":{"name":"search_liens","arguments":{"budget_usd": 2000, "states": "FL", "limit": 5}}}'

curl -s -X POST $MCP -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","id":4,"method":"tools/call",
       "params":{"name":"get_lien","arguments":{"lien_id": "<lien-uuid>"}}}'

Every result is a text content block whose text is JSON. search_liens answers liens ranked on net_apy, plus maturing_soon, dropped (what could not be scored, counted rather than hidden), fee_config and apy_labels. Keep the lien_id you want.

Step 2 — Get authorized (the human step)

First, check whether this step is already done. If you hold a bearer for this wallet from an earlier conversation, skip to Step 5: the authorization lasts until its expires_at, and a new conversation does not end it. If you are not sure whether the wallet is registered, ask LienFi, with no credential:

curl -s https://api.lienfi.com/api/v1/agents/<agent-wallet-address>

It answers registered, expiresAt and revokedAt. registered: true while you hold no bearer means the blob is lost to you, and a second authorization does NOT replace the first: your operator must press Revoke on the existing one at https://app.lienfi.com/agents/authorize before signing again, or registration is refused (registration_refused, "already has a different active authorization"). Say so before they sign, not after the refusal.

Then tell your operator, in these words: go to https://app.lienfi.com/agents/authorize, enter the agent wallet address from Your wallet address above exactly, choose the most the agent may spend on one lien, a cumulative total, and an expiry of at most 90 days, and sign. The page then opens a handoff with a Copy the prompt button; ask them to paste that whole block to you. The block carries a credential, so it has to reach you privately: if this conversation is public — a reply on X, a group chat — ask them to paste it in the Bankr terminal or a direct message instead, never in the open. It carries all four of:

  1. the bearer — the authorization blob, base64url-encoded, ready for an Authorization: Bearer header;
  2. the key-proof typed data, with the authorization digest filled in;
  3. one consent typed data per required agreement;
  4. the ready registration call, over MCP and over REST.

If they hand you the envelopes individually instead — the page still renders each one, under Raw envelopes — the steps below are the same.

Wait. Do not poll LienFi for it, and do not retry a refused tool while you wait.

Step 3 — Sign the key proof and the consents (your wallet)

For the key proof and for EACH consent envelope: set message.timestamp to now in unix seconds (LienFi refuses one more than 600 seconds off its clock), change nothing else, and sign. Inside Bankr: your wallet tool's eth_signTypedData_v4 over the envelope. Over the Wallet API:

curl -s -X POST https://api.bankr.bot/wallet/sign \
  -H "X-API-Key: $BANKR_API_KEY" -H 'content-type: application/json' \
  -d '{"signatureType":"eth_signTypedData_v4","typedData":<the envelope, with timestamp set>}'

Either way you get a signature (the Wallet API answers { "success": true, "signature": "0x…", "signer": "0x…" }). Keep each signature with the timestamp you signed. The envelopes are described field by field in references/typed-data.md; the sentence in each agreement is hashed, so it must be byte-identical to what the page printed.

Step 4 — Register

Over MCP, with the bearer:

curl -s -X POST $MCP -H 'content-type: application/json' \
  -H "Authorization: Bearer $LIENFI_BEARER" \
  -d '{"jsonrpc":"2.0","id":5,"method":"tools/call",
       "params":{"name":"register_agent","arguments":{
         "agent_key_proof": {"specVersion":"agent-keyproof-v1","signature":"0x…","timestamp":1756800000},
         "agent_consents": [
           {"specVersion":"consent-v2","documentType":"terms-and-conditions","version":3,"signature":"0x…","timestamp":1756800000},
           {"specVersion":"consent-v2","documentType":"wallet-connection-consent","version":1,"signature":"0x…","timestamp":1756800000}
         ]}}}'

Use the documentType and version values the page printed — they are the versions LienFi currently publishes. The answer is registered: true. The same body also works as POST https://api.lienfi.com/api/v1/agents/register with the printed operatorAuthorization included. Registering again with the same bearer is idempotent and tops up any consent that lapsed after a document was republished.

From now on send the bearer on every LienFi call.

Step 5 — Check yourself, then price

curl -s -X POST $MCP -H 'content-type: application/json' -H "Authorization: Bearer $LIENFI_BEARER" \
  -d '{"jsonrpc":"2.0","id":6,"method":"tools/call","params":{"name":"agent_status","arguments":{}}}'

curl -s -X POST $MCP -H 'content-type: application/json' -H "Authorization: Bearer $LIENFI_BEARER" \
  -d '{"jsonrpc":"2.0","id":7,"method":"tools/call","params":{"name":"quote_lien","arguments":{"lien_id":"<lien-uuid>"}}}'

agent_status is the first call to mak

Truncated for display — read the full file on GitHub.

Related Skills

View on GitHub
GitHub Stars1.2k
CategoryEducation
Updated1mo ago
Forks629

Languages

JavaScript

Trust signals

88/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

1 medium