Install Jentic One Beta

Connect the MoveSurge Institutional Events API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the MoveSurge Institutional Events 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%2Fmovesurge.com%2Fmovesurge" | 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%2Fmovesurge.com%2Fmovesurge" | 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 MoveSurge Institutional Events API.

List curated market-moving events filtered by comma-separated ticker symbols and categories

Restrict the event feed to items at or above a min_impact level of low, medium, high, or critical

Resume an event feed after a disconnect using the published_after or updated_after watermark

Retrieve one event by its stable public event ID with headline, classification, instruments, and market reaction

GET STARTED

Start building with MoveSurge Institutional Events API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use MoveSurge Institutional Events API for, with concrete tasks.

★ AI research agent briefing on market-moving news

An AI agent preparing a morning brief needs curated events rather than a raw headline firehose. Through Jentic the agent searches for 'list market-moving events for a symbol', loads the MoveSurge events operation with its input schema, and calls it with a symbols filter and a high min_impact threshold while the bearer key is injected at call time. It returns headlines, affected instruments, and measured reactions for the watchlist without the developer hand-wiring the client.

Call GET /api/v1/events/ with symbols=AAPL,NVDA and min_impact=high, then summarise each event's headline and market reaction

Reconnect recovery for an event-driven trading monitor

A monitoring service that consumes the MoveSurge WebSocket stream can miss events while it is disconnected. On reconnect it calls the events list with the updated_after watermark set to the last update it processed, which returns every event created or revised since then, and pages through with the opaque cursor until has_more is false. The monitor's local state then matches the curated feed before it resumes streaming.

Call GET /api/v1/events/ with updated_after=2026-11-09T08:00:00Z, follow paging.next_after until has_more is false, and upsert each event by event_id

Event study on measured market reactions

A quant analyst studying how markets respond to a category of news pulls historical events for a set of categories within the desk's contracted history window. Each MoveSurge event carries a market_reaction block alongside its classification, so the analyst can group reactions by impact level and category without joining a separate price dataset for the first pass.

Page GET /api/v1/events/ with categories=macro and min_impact=medium back through the history window using paging.next_before, then tabulate market_reaction by impact level

Desk credential and quota health check

Before a scheduled job pulls events, it confirms the desk key works and reads how much history and throughput the contract allows. The MoveSurge health route returns the credential environment, granted scopes, history_days, requests_per_minute, and the maximum WebSocket connections, so the job can size its paging and fail fast on a bad key.

Call GET /api/v1/health/ and report the desk's history_days, requests_per_minute, and max_websocket_connections

Key Endpoints

6 endpoints — the movesurge institutional events api serves a rolling history of curated market-moving news events, each tagged with the instruments it touches, an impact level, an analysis block, and a measured market reaction.

METHOD

PATH

DESCRIPTION

GET

/api/v1/events/

List curated events with filters and cursors

GET

/api/v1/events/{event_id}/

Retrieve one event by public ID

GET

/api/v1/health/

Check credential and contracted-window health

GET

/api/v1/schema/

Get JSON Schema and protocol reference

GET

/api/v1/openapi.json

Get the public API specification

GET

/api/v1/events/

List curated events with filters and cursors

GET

/api/v1/events/{event_id}/

Retrieve one event by public ID

GET

/api/v1/health/

Check credential and contracted-window health

GET

/api/v1/schema/

Get JSON Schema and protocol reference

GET

/api/v1/openapi.json

Get the public API specification

Why Jentic?

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

Setup

Wiring MoveSurge by hand means sending a desk key as a bearer token, handling opaque before and after cursors, and choosing between publication and update watermarks for recovery. Through Jentic you install once, import MoveSurge from the API Directory, store the desk key once, and your agent calls it.

Permission scoping

MoveSurge is a read-only feed, and rules filter on method and path, so you can bound your agent to the event list and event detail operations under /api/v1/events/. You choose the operations it may call, so the health and schema routes are not included unless you add them.

Credential isolation

Your MoveSurge desk 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 'list market-moving events for a symbol' or 'get a news event by ID', and Jentic returns the matching MoveSurge operation with its input schema, including the symbols and min_impact filters, so the agent calls the right route directly.

FAQs

Specific to using MoveSurge Institutional Events API through Jentic.

What authentication does the MoveSurge Institutional Events API use?

Per its OpenAPI spec, the MoveSurge API uses HTTP bearer authentication with a desk API key sent as Authorization: Bearer on the health, schema, and events routes. The public spec document at GET /api/v1/openapi.json and the integration guide at GET /docs/api/v1/ need no key. Through Jentic the desk key is held by your own instance and attached at call time, so the agent never handles it.

Can I filter MoveSurge events by ticker and impact level?

Yes. GET /api/v1/events/ accepts a comma-separated symbols filter, a comma-separated categories filter, and a min_impact threshold with values low, medium, high, or critical, plus a limit of up to 200 per page. Results page with the opaque before and after cursors, and published_after or updated_after let a client resume from a watermark.

What are the rate limits for the MoveSurge Institutional Events API?

The OpenAPI spec does not publish a fixed number. Limits are set per desk contract: GET /api/v1/health/ returns your desk's `requests_per_minute` and `max_websocket_connections`, and over-limit calls return HTTP 429. See https://movesurge.com/docs/api/v1/ for the integration guide.

How do I pull high-impact events for a watchlist through Jentic?

Search Jentic for 'list market-moving events for a symbol', load the GET /api/v1/events/ operation, and execute it with symbols set to your tickers and min_impact set to high. The response carries each event's headline, instruments, analysis, and market reaction. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Can I limit what my agent is allowed to do with the MoveSurge API?

Yes. Write a rule that allows only the events list and single-event read operations, and the agent can query the curated feed and open individual events but cannot call anything else on your desk key. Each call it makes is logged so you can review what it read.

Does the MoveSurge API return live prices?

No. MoveSurge delivers news events and a measured market reaction attached to each event, not a tick, quote, OHLC, or order-book feed. Its real-time channel is a WebSocket stream of events described in the spec's x-websocket block, separate from the REST routes.

MoveSurge Institutional Events API

AI ReadinessFoundational (C)55/100

See full scorecard

Official vendor OpenAPI document · agent-readyFinanceBankingbearer6 EndpointsREST

For Agents

List and fetch curated market-moving news events from MoveSurge, filtered by symbol, category, and impact, with each event's instruments, analysis, and measured market reaction.

Use for: List all high-impact market events for AAPL and MSFT, Get the latest critical news events across every symbol, Retrieve the full detail of a MoveSurge event by its ID, Find all events published after a given timestamp

Not supported: Does not provide price quotes, OHLC candles, order books, or trade execution. Use for curated market-moving news events and their measured reactions only.

The MoveSurge Institutional Events API serves a rolling history of curated market-moving news events, each tagged with the instruments it touches, an impact level, an analysis block, and a measured market reaction. Clients list events filtered by ticker symbols, categories, and a minimum impact threshold, page backward or forward with opaque cursors, and resume after a disconnect from a publication or update watermark. A single event can be fetched by its stable public ID, and a health route reports the desk's contracted history window and per-minute request allowance. Real-time delivery runs over a separate WebSocket stream that pushes events, not prices.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: C-Signals: 4

91%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

Specification Validity

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

17%

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.

42%

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: FSignals: 4

41%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

67%

OperationId Quality

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

46%

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: CSignals: 1

54%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the MoveSurge Institutional Events API to your agent

Capabilities

Start building with MoveSurge Institutional Events API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

MoveSurge Institutional Events API

Jentic AI Readiness Score

MoveSurge Institutional Events 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