plugin.json
The manifest: name, version, and what the package provides. The repository carries both the Agent Plugins 1.0.0 layout and the near-identical Claude Code variant, so either loader works.
AGENT PLUGIN · SPEC 1.0.0
The official TickerLayer Agent Plugin packages the hosted MCP endpoint and a market-data skill into one portable folder, following the vendor-neutral Agent Plugins 1.0.0 open spec. Install it with one command and your agent client gets typed market-data tools plus the guidance to use them well.
INSIDE THE PACKAGE
A plugin is just a folder in an open format — inspectable in the repository before you install anything.
The manifest: name, version, and what the package provides. The repository carries both the Agent Plugins 1.0.0 layout and the near-identical Claude Code variant, so either loader works.
Usage guidance an agent reads before calling tools — symbol conventions, a discovery-first workflow, error handling, and market-calendar awareness — in the open agentskills.io format.
Points the client at the hosted MCP endpoint: ten typed tools across seven asset classes, nothing to run locally, and the same server every other integration path uses.
ONE-COMMAND INSTALL
The same package installs across clients. Commands are current as of August 2026; the repository README stays authoritative as client tooling evolves.
/plugin marketplace add tickerlayer/agent-plugin
/plugin install tickerlayerAUTH & SECRETS
Nothing sensitive ships in the plugin. Each client authenticates at connect time, and every request runs under your TickerLayer account's plan, rate limits, and monthly quota.
OAuth sign-in: OAuth-capable clients open the TickerLayer sign-in the first time they connect to the MCP server. Approve once — no key to copy or store.
API key: clients that support custom headers keep using the x-api-key header from your dashboard, exactly as before. Nothing existing changes.
Never: commit a key into the plugin folder, a fork of the repository, or any client config you share. The package is designed to stay secret-free.
ONE STACK, FIVE ENTRY POINTS
Whichever side of today's agent stack you're on, TickerLayer is ready. The plugin bundles the MCP endpoint and skills into a portable install; everything underneath stays the same.
Read more: MCP server · x402 pay-per-call · llms.txt · AI & Agents hub.
AGENT PLUGIN FAQ
An open packaging spec, one public repository, and authentication that stays in the client.
Agent Plugins 1.0.0 is a vendor-neutral open packaging spec for distributing agent capabilities, published in August 2026 at agent-plugins.org and governed by a cross-vendor technical steering committee. A plugin is a portable folder: a plugin.json manifest, skills that teach an agent how to use a product, and an mcp.json that points at MCP servers.
No. The plugin is not an alternative to MCP — it packages the hosted MCP endpoint together with usage skills into one portable install. Connected clients still call the same MCP server and the same ten tools; the plugin removes the per-client configuration step and adds guidance the agent can read.
As of August 2026: Claude Code and Codex CLI through their plugin marketplace commands, Cursor through /add-plugin, and VS Code with GitHub Copilot through “Chat: Install Plugin From Source”. The ChatGPT app skips the package and connects to the same hosted MCP server directly as an OAuth developer-mode connector.
No. The package contains no secrets, ever. Authentication happens in the client at connect time: an OAuth sign-in with your TickerLayer account, or the x-api-key header in clients that support custom headers.
The plugin itself is free and open source. Data usage runs under your TickerLayer account — your plan's entitlements, rate limits, and monthly quota apply to every tool call, exactly as with a direct MCP or REST integration.
Distribution is git-based. Reinstall the plugin, or use your client's plugin-update command, to pull the latest manifest and skills from the repository. The hosted MCP endpoint the plugin points at updates server-side, with no action needed.
Symbol conventions (stocks always use the MARKET:SYMBOL form), a discovery-first workflow that lists valid symbols before querying, error handling for plan-entitlement responses, and market-calendar guidance so agents check sessions and holidays instead of assuming a market is open.
PORTABLE BY DESIGN
Add the plugin from the repository, sign in or paste a key when your client asks, and your agent gets the same typed market data everywhere.