Can AI agents automate Monta?

Monta is automatable today through the Partner API. This record is Monta's charge-point software and the Partner API. It is not Tibber, Zaptec, or Easee hardware. The API base in the OAuth guide is https://partner-api.monta.com/api/v1. Partner apps use OAuth 2.0 authorization code with client_secret_post. Access tokens last one hour, refresh tokens rotate and last 30 days, and API calls send Authorization Bearer. The issuer URL is listed as On Request, and the OAuth handshake exists in production only. Each install has a default budget of 1,000 requests per 60 seconds. Install webhooks are signed with HMAC-SHA256 and the guide says delivery is best-effort. A separate webhooks page says entity webhooks are for selected partners. Monta documents two MCP servers. The account server at https://partner-api-mcp.monta.app/mcp exposes one tool per API endpoint, described as 180 or more, filtered by credential scopes. The docs server at https://docs.partner-api.monta.com/mcp is anonymous. The CLI monta, installed as @monta-api/cli, says every endpoint is a command and defaults to pretty JSON. A registry search for monta did not return this server on the first page. That is not proof of absence. No language SDK page was opened. Computer-use viability is unassessed. API and MCP both score 8. API is the best path because the MCP account server is a wrapper over the same credentialed API, and the OAuth issuer is not printed in the public guide. The CLI scores 7.

Best path today: api · Overall automatability: 8/10