How Gilver works.

Gilver draws the market instead of tabulating it. Gold, silver and bitcoin become objects you can turn, compare and watch move, and every view reads the same price feed underneath. If you have used a terminal before, the three views will feel familiar. The difference is that you watch them rather than scan them. Proper walkthroughs go here.

Assets is the 3D terminal: gold, silver and bitcoin as physical objects, where size and motion carry price and sentiment. Capital Flow puts cash, metals, bonds, stocks and crypto on one diagram, so you can see which way money is leaning. Intelligence is the reading of all that: the macro backdrop, the levels people are watching, and what could move things next.

A separate ingester polls the providers and writes gold, silver and bitcoin into a Redis cache about every five seconds. The app reads that cache, not the providers. Spot prices are served to clients straight from cache. Prices come from Binance, CoinGecko, CoinMarketCap, CNBC, Yahoo Finance, Twelve Data, Polygon, FMP and gold-api. Stocks, precious metals and FX come from Twelve Data, crypto from CoinMarketCap, money-market cash from the U.S. Office of Financial Research, and revenue and earnings from SEC XBRL filings. Freshness, staleness and weekend handling will be documented here.

Read endpoints exist today. The one worth knowing is GET /api/prices/redis/all, which returns gold, silver and bitcoin in one response straight from the cache. The full list, payload shapes, caching headers and rate limits aren't documented yet, so treat anything you find by poking around as subject to change.

Three pieces run side by side: the feed, the worker and the API. Getting them up on your own machine takes environment setup that nobody has written down yet. Ask us in the meantime and we'll walk you through it.

There are no accounts yet — nothing to sign in to, no API keys, no tiers. Use the terminal as it is. When that changes, key handling and request signing get explained here.