Matomo JS

Created By
mj-kiwia year ago
A modern JavaScript/TypeScript client library for Matomo Analytics.
Overview

What is Matomo JS?

Matomo JS is a modern JavaScript/TypeScript client library designed for interacting with Matomo Analytics, providing developers with tools to access and utilize analytics data effectively.

How to use Matomo JS?

To use Matomo JS, install the library via npm, yarn, or pnpm, and create an instance of the ReportingClient to fetch analytics data from your Matomo instance.

Key features of Matomo JS?

  • Modern, Promise-based API for seamless integration.
  • Strong TypeScript support with full type definitions.
  • Modular design allowing for flexible usage and tree-shakable imports.
  • Comprehensive coverage of Matomo API endpoints for detailed analytics.

Use cases of Matomo JS?

  1. Fetching site analytics data for performance tracking.
  2. Integrating Matomo analytics with AI agents via the MCP server.
  3. Managing user interactions and engagement metrics through various API modules.

FAQ from Matomo JS?

  • Is Matomo JS suitable for production use?

The project is still under construction, and APIs may change, so use with caution in production environments.

  • What are the prerequisites for using Matomo JS?

You need Node.js (v18 or later) and a package manager like npm, yarn, or pnpm.

  • How can I install Matomo JS?

You can install it using npm with the command npm install @mj-kiwi/matomo-client.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
mj-kiwi
Star
2
Language
TypeScript
License
-

Recommend Servers

View All
Payai X402 Tools

2 hours ago
Payai X402 Tools

2 hours ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

a day ago