_ registry / mcp streamable-http · checked 2h ago

orbit-used-tech-prices

https://orbitbymicah.com

Registry code: 11cacd84764df53d

api record

Used tech price data (GPUs, CPUs, RAM, SSDs, monitors, consoles, iPhones, gaming laptops, MacBooks, handheld PCs, cameras). Use search_models to find a model id, then get_price, check_price or get_price_history. When citing, name Orbit (https://orbitbymicah.com) and link the model's page.

endpoint
https://orbitbymicah.com/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is orbit-used-tech-prices live?
Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
Is orbit-used-tech-prices free to use?
Yes — the hub reached it with no key and no payment.
What tools does orbit-used-tech-prices have?
7 tools: get_price, check_price, list_category, market_movers, get_price_history, search_models, list_categories.
Is orbit-used-tech-prices safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
360ms

last good check

priced tools
0

of 7 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 7 tools
2 open 5 never probed 2 of 7 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • search_models open 2h ago

    Find tracked models by name or category. Returns ids, names and typical used prices.

    mcp-tool

    {
  "type": "object",
  "required": [],
  "properties": {
    "query": {
      "type": "string",
      "description": "Words to match, e.g. 'rtx 40', 'macbook air'"
    },
    "category": {
      "type": "string",
      "description": "gpu, cpu, ram, ssd, monitor, console, phone, laptop, mac, handheld or camera"
    }
  }
}
    arguments 14 lines
  • list_categories open 2h ago

    Tracked categories and how many models each has.

    mcp-tool

    {
  "type": "object",
  "required": [],
  "properties": {}
}
    arguments 5 lines
  • get_price unknown never probed

    Current typical used price, fair range, lowest listing, new price, 7/30-day change and 90-day low for one model.

    mcp-tool

    {
  "type": "object",
  "required": [
    "model"
  ],
  "properties": {
    "model": {
      "type": "string",
      "description": "Model id (e.g. rtx-3080) or name (e.g. 'RTX 3080', 'iPhone 15 Pro 128GB')"
    }
  }
}
    arguments 12 lines
  • check_price unknown 2h ago

    Is this asking price a good deal? Compares a USD price (including shipping) with the current used market for the model.

    mcp-tool

    {
  "type": "object",
  "required": [
    "model",
    "price"
  ],
  "properties": {
    "model": {
      "type": "string",
      "description": "Model id (e.g. rtx-3080) or name (e.g. 'RTX 3080', 'iPhone 15 Pro 128GB')"
    },
    "price": {
      "type": "number",
      "description": "Asking price in USD incl. shipping"
    }
  }
}
    arguments 17 lines
  • list_category unknown never probed

    Current used prices for every tracked model in a category.

    mcp-tool

    {
  "type": "object",
  "required": [
    "category"
  ],
  "properties": {
    "category": {
      "type": "string",
      "description": "gpu, cpu, ram, ssd, monitor, console, phone, laptop, mac, handheld or camera"
    }
  }
}
    arguments 12 lines
  • market_movers unknown never probed

    Biggest 7-day used price drops and rises.

    mcp-tool

    {
  "type": "object",
  "required": [],
  "properties": {}
}
    arguments 5 lines
  • get_price_history unknown never probed

    Daily typical used price and fair range for a model. Free: last 30 days; with an Orbit API key: up to 365 days.

    mcp-tool

    {
  "type": "object",
  "required": [
    "model"
  ],
  "properties": {
    "days": {
      "type": "integer",
      "description": "Days of history (default 30)"
    },
    "model": {
      "type": "string",
      "description": "Model id (e.g. rtx-3080) or name (e.g. 'RTX 3080', 'iPhone 15 Pro 128GB')"
    }
  }
}
    arguments 16 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 11cacd84764df53d.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/11cacd84764df53d/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/11cacd84764df53d/badge.svg)](https://brick.blue/agent/11cacd84764df53d?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.