API Acre

What API Acre MCP server does

API Acre MCP server provides 34 tools for agents working with web, document, SEC, developer, data, and EVM-related capabilities. The available description identifies the tool categories but does not provide individual tool names, parameter lists, response formats, or examples. Developers should therefore treat the category list as the supported scope and verify the exact operations before building an integration around a specific workflow.

The service is described as pay-per-call. That means usage is associated with individual tool calls rather than being presented as an unlimited free interface. The supplied material does not state pricing, quotas, billing limits, or whether every tool uses the same rate.

How it works

API Acre MCP server uses x402 on Base for payment. The available information establishes the payment network and mechanism, but does not explain wallet requirements, settlement flow, supported assets, authentication steps, or how failed payments are handled. Those details are important to confirm before deploying it in an automated agent workflow.

The source identifies API Acre as an MCP server, so it is intended to expose its listed capabilities to an MCP-compatible agent or client. However, no transport type, installation command, configuration file, endpoint, or client-specific setup is provided. This page cannot establish whether the service runs locally, connects to a hosted endpoint, or requires a separate package.

Tools and capabilities

The API Acre MCP server groups its 34 pay-per-call tools into six stated areas:

• Web tools for web-oriented tasks.
• Document tools for document-related tasks.
• SEC tools for working with SEC-related information.
• Developer tools for development workflows.
• Data tools for data-oriented operations.
• EVM tools for EVM-related operations.

These labels describe the available domains, not guaranteed individual actions. The source does not specify whether the tools read, search, transform, submit, or mutate data within each category. Confirm the published API documentation for exact behavior and required inputs.

Limitations and notes

The available material is limited to a short description and does not include a README. It does not document installation, environment variables, supported MCP clients, authentication beyond the x402 reference, pricing, rate limits, licensing, error handling, or tool schemas. As a result, API Acre MCP server can be evaluated confidently at the category level, but a production integration requires additional documentation from the provider.

The clearest fit is an agent that needs several of the listed web, document, SEC, developer, data, or EVM capabilities and can support pay-per-call usage through x402 on Base. If an application needs fixed pricing, offline execution, a named client integration, or documented local deployment, those requirements are not confirmed by the supplied information.