Is there an AgentFilings MCP server?

You don't need an MCP server to give your agent AgentFilings. Jentic connects it directly from the API Directory: import AgentFilings and your agent reads filings, earnings, and insider data straight away. Operations are discovered on demand, so no extra server's tool definitions sit in your agent's context.

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

Yes. AgentFilings carries no resource id in its paths, so rules bound which operations the agent may call rather than which ticker. You can allow only the filings and earnings reads, so the agent retrieves company data and nothing else, and the paid insider-transactions endpoint stays out of the rule unless you add it.

Can I get a company's earnings with the AgentFilings API?

Yes. The earnings summary endpoint returns a structured summary built from XBRL company facts, so you read normalized figures as JSON without parsing a PDF. The data is public-domain SEC information kept pre-parsed, and the probe endpoint reports how fresh it is before you request it.

What are the rate limits for the AgentFilings API?

The AgentFilings OpenAPI spec does not publish request rate limits. Pricing is per endpoint and is returned by the free probe endpoint along with coverage and freshness timestamps, so an agent checks cost and availability before paying with x402. Check the AgentFilings documentation at https://agentfilings.com for current details.

How do I get SEC filings with the AgentFilings API through Jentic?

Search the Jentic API Directory for an intent like 'get the latest filings for a ticker', import AgentFilings, and your agent calls the probe and filings operations through Jentic. To run it on your own infrastructure, install Jentic One from its GitHub repo.