Przejdź do treści
Biblioteka skilli
Finanse i księgowość · Integracja z narzędziem

rotki-api

/rotki-api

Obsługuje lokalną aplikację rotki przez REST API i serwer MCP, wyjaśnia pokrycie indeksatorów EVM oraz kwestie dopasowania transakcji mostów.

Repozytorium
ai-config ↗
Licencja
GPL-3.0
Ostatnia zmiana repozytorium
08.11.2026

Ocena i bezpieczeństwo

100/ 100Klasa: dobry
Format25 / 25
Frontmatter z nazwą i opisem, poprawna nazwa, opis do 1024 znaków, nazwa zgodna z folderem.
Odkrywalność25 / 25
Opis mówi, kiedy użyć skilla, ma sensowną długość i jest w 3. osobie.
Treść35 / 35
Co najmniej 150 słów i do 500 linii, nagłówki, listy kroków, przykłady albo kod.
Higiena15 / 15
Bez zaślepek typu TODO, bez ścieżek Windows, z licencją.
Ryzykobrak sygnałów w skanie
Pliki w paczce
3
Skrypty
0
Komentarze HTML
0
Adresy URL w SKILL.md
4
Przestarzałość

Brak sygnałów. Repozytorium zmienione 08.11.2026, bez odwołań do wycofanych modeli i API.

Licencja

GPL-3.0, otwarta.

Co robi i kiedy

Obsługuje lokalną aplikację rotki przez REST API i serwer MCP, wyjaśnia pokrycie indeksatorów EVM oraz kwestie dopasowania transakcji mostów.

Wyzwalacze z opisu

Internal Transaction Conflicts
Oryginalny opis (EN)

Drives a running rotki desktop app through its local REST API and MCP server, and explains rotki's EVM indexer coverage (Etherscan, Blockscout, Routescan free and paid tiers), bridge-transaction matching, internal-transaction conflicts and zkSync Lite quirks. Use when querying or changing rotki data from an agent, when rotki warns that an indexer or paid API key is needed, when chains such as Base, BSC, Optimism, Polygon or zkSync Lite are missing transactions, when matching bridge legs, when resolving "Internal Transaction Conflicts", or when deciding whether to use rotki's MCP server.

Jak działa

  1. Reaching the backend
  2. Missing transactions and indexer keys
  3. Bridge matching
  4. Internal transaction conflicts
  5. zkSync Lite
  6. Decode-time context
  7. Users' address books
  8. Secrets in rotki errors
  9. MCP server
Sekcje z nagłówków SKILL.md, w oryginale · 125 linii, 876 słów
Podgląd SKILL.md
---
name: rotki-api
description: Drives a running rotki desktop app through its local REST API and MCP server, and explains rotki's EVM indexer coverage (Etherscan, Blockscout, Routescan free and paid tiers), bridge-transaction matching, internal-transaction conflicts and zkSync Lite quirks. Use when querying or changing rotki data from an agent, when rotki warns that an indexer or paid API key is needed, when chains such as Base, BSC, Optimism, Polygon or zkSync Lite are missing transactions, when matching bridge legs, when resolving "Internal Transaction Conflicts", or when deciding whether to use rotki's MCP server.
---

# rotki API

rotki keeps a user's whole crypto accounting history. Every write changes
their books, so **get explicit approval for each write** (adding accounts,
matching or ignoring bridge legs, re-decoding, editing events, manual
balances), naming the endpoint, the effect and how to undo it. "Help me
match these" is a request for help, not approval. Reads need no approval.

## Reaching the backend

The desktop app's launcher (`starling`) runs the core and passes its ports
on the command line, so read them from the process instead of guessing:

```bash
ps -eo args | grep '[s]tarling'   # --core-port, --mcp-port, --proxy-port
```

The core API is `http://127.0.0.1:<core-port>/api/1/` (4242 by default),
with no authentication on the desktop. A user must be logged in.

Request quirks that cost time:

- Many GET endpoints take a JSON body, but a `Content-Type: application/json`
  header on a GET **without** a body returns HTTP 500 ("400 Bad Request:
  The browser (or proxy) sent a request...").
- Doc headings sometimes show a trailing slash (`/balances/manual/`); the
  real route has none and the slash gives 404.
- `POST /history/events` rejects `async_query`; most other endpoints accept
  it.
- Chain names differ by endpoint: the accounts path uses the
  `SupportedBlockchain` value (`BASE`, `BINANCE_SC`, `POLYGON_POS`,
  `ZKSYNC_LITE`), lookup and decode use lowercase chain names (`base`,
  `binance_sc`, `zksync_lite`), and history-event `location` filters use
  labels with spaces (`polygon pos`, `binance sc`, `zksync lite`).

For the endpoints used most and their payloads, read
[references/api-recipes.md](references/api-recipes.md).

## Missing transactions and indexer keys

rotki lists an address's transactions only through Etherscan, Blockscout
or Routescan, and the free tiers no longer cover several chains. Before
recommending a paid plan, read
[references/indexers-and-gaps.md](references/indexers-and-gaps.md): it
gives per-chain coverage, how to prove what is actually missing, and a
free route that feeds hashes from another source into rotki's lookup
endpoint, which fetches each transaction from RPC nodes.

## Bridge matching

The destination of an unmatched bridge leg is in the event's
`extra_data.bridge.to_chain` and `to_address`; read it before searching
time windows. Then pick the resolution by what really happened:

| Situation | Resolution |
|---|---|
| Counterpart exists in rotki | `PUT /history/events/match/bridges` with `matched_events` |
| Funds arrived but no transaction can ever be fetched: Polygon PoS deposits (credited by state sync, no transaction to the user), Optimism before the 11 Nov 2021 regenesis | `create_counterpart: true` (synthetic leg; unlinking deletes it) |
| Destination is the user's but untracked by rotki (e.g. Linea, chain 59144) | Ignore the leg (no `matched_events`), optionally add a manual balance |
| Funds really left the user | `external: true`, which books a payment and therefore a disposal |

Ignoring keeps the move a transfer; `external` changes the accounting.
Finding and changing matches needs premium; listing unmatched legs does not.

## Internal transaction conflicts

`all_zero_gas` means every stored internal-transaction row for a parent
transaction has `gas = '0'`, so rotki cannot tell good rows from bad
duplicates and wants to repull. "Resolve Selected" only repeats the repull
through the same indexers, so it keeps failing where no free indexer
serves the chain or era. Check the decoded amounts against an independent
source; if they agree, the conflict is harmless to the books.

Nothing else can clear one: no endpoint accepts internal-transaction data
or marks a conflict accepted, and rotki never traces through an RPC node,
so external traces (Alchemy, `cast run`) cannot be fed in. Leftovers are
not worth an upstream request: the queue is filled only by a one-off
migration in 1.42.1, and the code marks the table "temporary, to be
removed in a future release", which will drop them.

## zkSync Lite

- Adding a second zkSync Lite account fetches nothing if its history is
  older than the newest transaction already saved for any account:
  `fetch_transactions()` starts from a database-wide maximum
  ([rotki/rotki#13345](https://github.com/rotki/rotki/issues/13345)).
  Work around it by re-decoding the missing hashes with
  `PUT /blockchains/transactions/decode`, `chain: zksync_lite`, which
  fetches each by hash. Get the hashes from
  `https://api.zksync.io/api/v0.2/accounts/<address>/transactions?from=latest&limit=100&direction=older`.
- rotki has no zkSync Lite decoders for protocols such as Gitcoin's 2020
  zkSync checkout; transfers appear as plain spends to retag by hand.

## Decode-time context

Events are labelled with the accounts tracked when they were decoded. A
transfer decoded before its other side's account was added stays a plain
receive or spend (possibly income) until that hash is re-decoded.

## Users' address books

Identifying counterparties often tempts a search of the user's notes or
address books. Ask before searching them, and do not print their entries
(addresses or labels) into the transcript without permission. Report only
the conclusion asked for, e.g. "this address is yours".

## Secrets in rotki errors

Blockscout errors embed the full request URL, including `apikey=`, in
notifications, logs and the conflicts table's `last_error`
([rotki/rotki#13346](https://github.com/rotki/rotki/issues/13346)).
Redact `apikey=` from any rotki output before saving or quoting it.

## MCP server

rotki 1.44+ ships a local, **read-only** MCP server (premium capability
`mcp`, check `GET /premium/capabilities`). It offers SQL over a snapshot
of history events and balances, asset details, cached historical prices
and the event taxonomy. It cannot change anything, so fixes still go
through the REST API. Its default `balanced` privacy mode hashes
addresses and transaction hashes, which suits analysis but not debugging
specific transactions. The user starts it from Settings → MCP, which
shows the endpoint; the launcher's `--mcp-port` gives the port.
Pliki w paczce (3)
  • SKILL.md 7 KB
  • references/api-recipes.md 4 KB
  • references/indexers-and-gaps.md 3 KB

Wersje

W bazie nie ma innych skilli o nazwie rotki-api.

Migawka bazy z 13.11.2026 · wersja paczki 7425b66eafb2 (skrót SHA-256 całej paczki)

Pobrania w ostatnich 30 dniach: 0 · ranking

Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.

Podobne skille

  • 100web3-data
    Pobiera dane on-chain przez CLI Chainbase: holderów tokenów, portfele, ceny, transfery, domeny ENS i transakcje w wielu sieciach.
  • 100okx-dex-bridge
    Obsługuje mostkowanie tokenów między łańcuchami: wyceny, porównanie opłat, wybór najtańszej lub najszybszej trasy, calldata oraz śledzenie statusu transakcji.
  • 82ave-trade-chain-wallet
    Przygotowuje i podpisuje transakcje wymiany na DEX przez API AVE Chain Wallet: wycenę, niepodpisaną transakcję i wysyłkę na BSC, ETH, Base i Solana.
  • 100web3-dev
    Pomaga budować aplikacje web3, boty i skrypty, które czytają dane blockchain przez API Blockscout PRO z ponad 100 sieci EVM.
  • 100monitoring-cross-chain-bridges
    Monitoruje TVL, wolumen, opłaty i status transakcji mostów międzyłańcuchowych, porównuje trasy i śledzi transakcje mostów.
  • 100meganode-skill
    Udostępnia API infrastruktury blockchain NodeReal MegaNode dla ponad 25 sieci (BSC, Ethereum, opBNB, Optimism, Polygon, Arbitrum, Klaytn): JSON-RPC, Enhanced APIs, MegaFuel bez opłat gas, Debug i Trace oraz WebSocket.

Uwagi i zgłoszenia

Wiadomość trafi do Bartosza Sokolińskiego. Adres e-mail jest potrzebny tylko do odpowiedzi. Szczegóły w polityce prywatności.