Install Jentic One Beta

Connect the Moon Catcher Wire REST API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Moon Catcher Wire REST API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fmooncatcherwire.com%2Fmooncatcherwire" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fmooncatcherwire.com%2Fmooncatcherwire" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Moon Catcher Wire REST API.

Pull current crypto news stories for a ticker such as BTC, ranked by market impact

Filter stories to a topic slug from the topics listing or to breaking stories only

Limit results to stories from the last N hours with since_hours

Read per-story sentiment, impact, credibility, and source domain scores

GET STARTED

Start building with Moon Catcher Wire REST API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Moon Catcher Wire REST API for, with concrete tasks.

★ AI trading assistant that checks the news before answering

An agent asked about a token's price move needs the current headlines behind it. Through Jentic the agent searches for 'get crypto news for a ticker', loads the Moon Catcher Wire stories operation with its input schema, and sends the ticker and a since_hours window. The mcw_ portal key is attached by your own Jentic One instance, and the agent gets back stories ranked by impact with sentiment scores it can cite.

Call GET /stories with ticker BTC, since_hours 12, and limit 10, then summarise the three highest-impact stories with their sentiment

Breaking-news alerts for a crypto desk

A desk that watches for market-moving crypto news can poll the board for breaking stories only. The breaking_only filter returns stories flagged is_breaking, each with an impact score from 0 to 1 and the source domain, so an alerting job can forward only stories above a chosen impact threshold.

Call GET /stories with breaking_only true and since_hours 1, and post any story with impact above 0.7 to the alerts channel

Topic-level sentiment tracking

Analysts tracking a theme, such as a regulatory topic or a token ecosystem, can read the topics listing to find its slug and tickers, then pull stories for that topic. Averaging the per-story sentiment scores gives a quick read of whether coverage is leaning bullish or bearish.

Call GET /topics to find a topic slug, then call GET /stories with that topic and limit 60 and report the average sentiment

Key Endpoints

2 endpoints — the moon catcher wire rest api serves the stories on the moon catcher wire crypto news board as read-only json, ordered by market impact with the strongest first.

METHOD

PATH

DESCRIPTION

GET

/stories

List stories by market impact

GET

/topics

List the topic rules stories filter by

GET

/stories

List stories by market impact

GET

/topics

List the topic rules stories filter by

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring Moon Catcher Wire by hand means creating an mcw_ portal key, sending it as a bearer token, and knowing that topic filters must match a slug from the topics listing. Through Jentic you install once, import Moon Catcher Wire from the API Directory, store the key once, and your agent calls it.

Permission scoping

Both operations are reads, and filters like ticker and topic travel as query parameters rather than path segments, so rules bound which operations your agent may call, not which ticker it asks about. There is no write surface to exclude.

Credential isolation

Your Moon Catcher Wire portal key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'get crypto news for a ticker' or 'list news topics', and Jentic returns the matching Moon Catcher Wire operation with its input schema, including the ticker, topic, since_hours, and breaking_only parameters.

FAQs

Specific to using Moon Catcher Wire REST API through Jentic.

What authentication does the Moon Catcher Wire REST API use?

Per its OpenAPI spec, GET /stories uses HTTP bearer authentication with a portal API key in the form mcw_..., which the account holder creates in the Moon Catcher Wire portal. GET /topics is open and needs no key. Through Jentic the key is stored by your own Jentic One instance and attached at call time.

Can I filter crypto news by ticker with the Moon Catcher Wire REST API?

Yes. GET /stories accepts a ticker query parameter such as BTC, plus topic, since_hours, breaking_only, and a limit from 1 to 60 with a default of 20. An unknown topic returns a 400 error, so read the slugs from GET /topics first.

What are the rate limits for the Moon Catcher Wire REST API?

The OpenAPI spec does not specify rate limits. Check the Moon Catcher Wire authentication notes at https://mooncatcherwire.com/auth.md for current limits on portal keys.

Is there a Moon Catcher Wire MCP server?

Yes - Moon Catcher Wire describes its own MCP server, which uses OAuth tokens with the news:read scope. You can also connect the REST API directly through Jentic: your agent gets both endpoints from the spec without loading another server's tool definitions into its context, your portal key is injected at call time by your self-hosted instance instead of living in an MCP config, and your rules decide which operations the agent may call.

Can I limit what my agent is allowed to do with the Moon Catcher Wire REST API?

Yes. The API is read-only, so the question is which reads the agent makes. Write a rule that allows GET /stories and GET /topics, and every call the agent makes is logged so you can see which tickers and topics it pulled.

How do I get breaking crypto news through Jentic?

Search Jentic for 'get breaking crypto news', load the GET /stories operation, and execute it with breaking_only set to true and an optional ticker or since_hours. The response returns matched stories with headline, impact, and sentiment. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Moon Catcher Wire REST API

AI ReadinessAI-Aware (B-)60/100

See full scorecard

Official vendor OpenAPI document · agent-readySocial MediaSocial Listeningbearer2 EndpointsREST

For Agents

Read the Moon Catcher Wire crypto news board by ticker, topic, or recency, with per-story sentiment, impact, credibility, and breaking flags.

Use for: Get the latest crypto news for BTC, Find all breaking crypto stories from the last six hours, List all topics the news board filters by, Check whether there is bearish news on ETH today

Not supported: Does not return token prices, place trades, or publish stories. Use for reading the Moon Catcher Wire crypto news board only.

The Moon Catcher Wire REST API serves the stories on the Moon Catcher Wire crypto news board as read-only JSON, ordered by market impact with the strongest first. Each story carries its headline and drudge-style rewrite, summary, source domain, credibility, tickers, a sentiment score from -1 bearish to +1 bullish, an impact score from 0 to 1, and a breaking flag. Stories can be filtered by ticker, topic, recency in hours, or breaking status, and a topics listing returns the rules behind each topic slug. The board reflects the same editorial decisions as the website, and stories editors withhold are counted but not served.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

100

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A+Signals: 4

99%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

100%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: B-Signals: 4

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

50%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: D-Signals: 4

29%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

40%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: B-Signals: 1

60%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: DSignals: 1

44%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Moon Catcher Wire REST API to your agent

Capabilities

Start building with Moon Catcher Wire REST API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Moon Catcher Wire REST API

Jentic AI Readiness Score

Moon Catcher Wire REST API

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness