~/ domain/guavy.com.mdTHE AGENT-READABLE WEB

guavy.com valid

Guavy API

Guavy provides a comprehensive API for scored market sentiment, news, and trade signals across every market Guavy covers.

Visit publisher ↗
Authority
46 reach 5 · trust 10 · quality 16 · freshness 15
Tier
listed
llms.txt
https://guavy.com/llms.txt
Sections
20
Links
1
Size
51821 bytes
Popularity rank
#866594
Registered
2018-11-21
Country
United States Hosting inference
Hosting country
United States Hosting inference
Country evidence
No published address evidence collected yet
For agents
Informational: content or services for people, nothing to operate
First seen
2026-10-25T16:39:58.834Z
Last checked
2026-10-25T18:39:39.209Z
Badge
Agent Web Map badge for guavy.com

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-25T18:39:35.265Z. Cached copy · Source on guavy.com

---
description: Guavy API
alwaysApply: true
applyTo: "**"
downloadedFrom: https://guavy.com/llms.txt
version: 1.0.0
---

# Guavy API

Guavy provides a comprehensive API for scored market sentiment, news, and trade signals across every market Guavy covers.

## Getting Started

To use the API, you need an API key. You can sign up for one at [Sign up](https://guavy.com/auth/signup).

Authentication is done via the `Authorization` header:
`Authorization: Bearer YOUR_API_KEY`

## Token Budget & Response Headers

Every metered response reports your balance in headers, so you never have to guess: `x-tokens-cost` (what this call cost), `x-tokens-limit` / `x-tokens-remaining` (monthly), and `x-tokens-limit-today` / `x-tokens-remaining-today` (daily). The `remaining` values are net of any credit applied to the same request. A `401` budget refusal carries them too, with `x-tokens-cost` at `0` because nothing was charged.

## Errors

Standard HTTP status codes: `400` malformed request (e.g. a `strategy` outside `aggressive`/`conservative` — the response names the offending value), `401` missing/invalid key or exhausted budget (a budget refusal adds `error_code` `DAILY_TOKEN_LIMIT` or `MONTHLY_TOKEN_LIMIT`, `limit_type`, `resets_at` (when the limit lifts, UTC; null when it cannot be stated) and `upgrade_url`, so it can be told apart from a bad key without reading the message), `402` market not in your plan (not returned today, because every launched market is on every plan's Sandbox floor), `404` unknown resource, `429` rate limited (retry after the `Retry-After` header), `503` a data source we depend on is temporarily unavailable — the trade-simulator upstream, or the datastore behind the news, sentiment and trend endpoints (retry after `Retry-After`). Over REST we don't bill you for our failures: tokens charged for a `5xx`, or for a `404` that lands after we've already charged, are credited back — less a 1-token floor. MCP has no credit path: a tool call that fails after it was charged keeps its charge.

## Limits

`limit` is bounded per route: paginated endpoints (list-symbols, recent-buys, recent-sells, recommendations) cap at 1000 results per call — page further with `skip`; unpaginated series (trend-history, backtest-history) cap at 5000, set above the real series length so nothing reachable is truncated. `years` on backtests caps at 10.

## API Versions & Markets

There are two REST surfaces, and picking the wrong one is the most common integration error:

- **`/api/v1/...`** — **crypto only**, and frozen. Every route below under a bare `/api/v1` path resolves its symbol against crypto, whatever you ask for. v1 takes **no** `market` parameter: a `?market=` query string is silently ignored, so `/api/v1/instruments/scorecard/Gold?market=commodities` is a crypto lookup for "Gold" and 404s.
- **`/api/v2/{market}/...`** — the per-market surface. **`{market}` is a path segment, not a query parameter.** Valid values: `crypto`, `forex`, `commodities`, `stocks
…

Machine-readable: GET /v1/resolve?q=guavy.com · GET /v1/domain/guavy.com · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Own or manage this website?

If you own or manage guavy.com, you can update its listing and review file health, discovery activity and score history.

Manage this listing — optional

What verification unlocks

See how your site is discovered—and control what agents see.

  • See your website in the map

    Review your indexed topics, nearby publishers sharing headings, measured listing exposure and map snapshots in a private report for your website.

  • Control what agents see

    Edit your listing description, tags, public contact details and additional llms.txt paths. Publish your terms for automated access, attribution and pricing.

  • Make your profile eligible for search

    A valid, listed, unblocked, verified profile can appear in our publisher sitemap and become eligible for search-engine visibility. Search engines decide what to index and rank.

  • Appear in our llms-full.txt

    Eligible verified publishers are listed by name, with their file links and summaries, in the service overview agents can read.

Free. No account registration, backlink or payment required. Public discovery remains available without verification.

Verify your website—free

Preview the owner dashboard · All verification benefits

Let your coding agent verify it

If your coding agent is authorized to manage this website, paste these instructions into it.

Claim my listing on Agent Web Map for guavy.com:
1. POST https://agentwebmap.com/v1/sites/guavy.com/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://guavy.com/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/guavy.com/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/guavy.com).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.

agent web map / a clearer way in.API & MCP · Contact