hypersignal

Get a free API key

hl_request_free_key

When a premium tool asks for an API key, call this to instantly issue a free key with 100 monthly premium calls, no signup needed.

Instructions

Issue yourself a free API key, instantly and with no signup. The key grants 100 premium calls per month — enough to evaluate every premium tool. Send it as the X-API-Key header on later requests. Call this first if a premium tool says it needs a key. One active key per requester: calling again replaces the previous key and keeps the same monthly usage, so it is safe to call if you lost your key but is not a way to reset the quota.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "hl_request_free_key"
  }
}

Input Schema

Name	Required	Description	Default
`acknowledge`	No	Acknowledges that analytics are informational and not investment advice.

Output Schema

Name	Required	Description	Default
`tier`	Yes
`apiKey`	Yes
`header`	Yes
`upgrade`	Yes
`reissued`	Yes
`usedThisMonth`	Yes
`monthlyPremiumCalls`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.5.0Jul 26, 2026

TDQS

A4.3/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations show non-read-only, non-destructive. Description adds that calling again replaces the key but keeps quota, safe if lost but not a quota reset. This behavioral detail goes beyond annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four well-structured sentences with no redundancy. Front-loaded with core action, then quota info, then usage hint, then repeat-call behavior. Every sentence is valuable.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 1 optional boolean param (100% schema coverage), presence of output schema, and low complexity, the description fully covers purpose, usage, behavior, and continuation (X-API-Key header). No gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Single boolean parameter 'acknowledge' with schema description covering it fully. Description does not add new meaning beyond schema, so baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb 'issue' and resource 'free API key', with instant and no signup. It uniquely distinguishes from sibling tools that are all trading/data operations.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says 'call this first if a premium tool says it needs a key'. Also explains behavior on repeated calls (replaces previous key, same monthly usage). Does not state when not to use, but context is clear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server