@mintapi/openclaw-mintapi is an OpenClaw plugin that exposes selected MintAPI paid endpoints as native OpenClaw tools.
It is built for agents and operator workflows that need paid access to social and video data inside OpenClaw while delegating payment signing to your own infrastructure.
The plugin registers OpenClaw tools backed by MintAPI. Requests go through the public MintAPI buyer SDK, which handles 402 Payment Required flows and retries with payment attached after resolving a signer from your configured signer module.
The plugin does not hold seller credentials or private keys.
Twitter/X:
mintapi_twitter_user_infomintapi_twitter_user_timelinemintapi_twitter_followersmintapi_twitter_followingmintapi_twitter_searchmintapi_twitter_latest_repliesmintapi_twitter_tweet_infomintapi_twitter_user_repliesmintapi_twitter_trends
YouTube:
mintapi_youtube_video_infomintapi_youtube_channel_videosmintapi_youtube_channel_aboutmintapi_youtube_playlistmintapi_youtube_relatedmintapi_youtube_transcriptmintapi_youtube_commentsmintapi_youtube_search
- OpenClaw with plugin support enabled
- Node.js compatible with your OpenClaw runtime
- a signer module that can satisfy MintAPI payment challenges
openclaw plugins install npm:@mintapi/openclaw-mintapi
openclaw plugins enable mintapiIf your OpenClaw setup does not hot-reload plugins, restart the gateway after install.
Configure the plugin under plugins.entries.mintapi.config:
{
plugins: {
entries: {
mintapi: {
enabled: true,
config: {
baseUrl: "https://api.mintapi.dev",
signerModule: "/absolute/path/to/signer-module.mjs",
preferredNetworks: ["base", "polygon", "solana"]
}
}
}
}
}Config fields:
baseUrl: optional, defaults tohttps://api.mintapi.devsignerModule: required unlessMINTAPI_SIGNER_MODULEis setpreferredNetworks: optional ordered payment network preference
Relative signerModule paths such as ./signers/mintapi.mjs are resolved relative to the plugin root.
This plugin uses the public MintAPI buyer SDK package @mintapi/gateway and expects a signer module compatible with that SDK.
In practice, your signer module should export a signer module created with defineSignerModule(...) or another supported resolver shape from @mintapi/gateway/client.
Example:
import { defineSignerModule } from "@mintapi/gateway/client";
export default defineSignerModule({
preferredNetworks: ["base", "polygon", "solana"],
signerResolversByFamily: {
evm: async ({ network }) => {
throw new Error(`Provide an EVM signer for ${network}`);
},
svm: async ({ network }) => {
throw new Error(`Provide an SVM signer for ${network}`);
},
},
});Starter file:
The plugin returns MintAPI responses as text content in the OpenClaw tool result. Most tools are thin wrappers over MintAPI endpoints and keep parameter names aligned with MintAPI where practical.
mintapi_twitter_user_info
screenname: requiredrest_id: optional
Example:
{
"screenname": "elonmusk"
}mintapi_twitter_user_timeline
screenname: requiredrest_id: optionalcursor: optional
mintapi_twitter_search
query: requiredsearch_type: optionalcursor: optional
mintapi_twitter_followers
screenname: requiredcursor: optionalblue_verified: optional
mintapi_twitter_following
screenname: requiredrest_id: optionalcursor: optional
mintapi_twitter_latest_replies
id: requiredcursor: optional
mintapi_twitter_tweet_info
id: required
mintapi_twitter_user_replies
screenname: requiredcursor: optional
mintapi_twitter_trends
country: required
Example:
{
"country": "UnitedStates"
}mintapi_youtube_video_info
id: requiredextend: optionalgeo: optionallang: optionalfields: optional
mintapi_youtube_channel_videos
id: optionalforUsername: optionalsort_by: optionaltoken: optionalgeo: optionallang: optionallocal: optionalfields: optional
mintapi_youtube_channel_about
id: optionalforUsername: optionalgeo: optionallang: optionalfields: optional
mintapi_youtube_playlist
id: requiredtoken: optionalgeo: optionallang: optionalfields: optional
mintapi_youtube_related
id: requiredtoken: optionalgeo: optionallang: optionalfields: optional
mintapi_youtube_transcript
id: requiredparams: optionallang: optional
mintapi_youtube_comments
id: requiredtoken: optionalsort_by: optionalgeo: optionallang: optionalfields: optional
mintapi_youtube_search
query: requiredtype: optionalduration: optionalupload_date: optionalsort_by: optionaltoken: optionalgeo: optionallang: optionalfeatures: optionallocal: optionalfields: optional
- request execution goes through
@mintapi/gateway - when MintAPI returns a payment challenge, the SDK resolves a signer using your signer module
- the plugin retries the request with payment attached
- results are returned as OpenClaw tool content
Plugin loads but tool calls fail immediately
- verify
plugins.entries.mintapi.enabledistrue - verify
signerModulepoints to a real file - if you use a relative signer path, verify it is relative to the plugin root
Missing signer module or requires signerModule
- set
plugins.entries.mintapi.config.signerModule - or set
MINTAPI_SIGNER_MODULEin the OpenClaw runtime environment
Payment challenge cannot be satisfied
- your signer module is loading, but it is not returning a signer that matches one of the accepted payment networks
- align
preferredNetworkswith the signer families you actually support
A tool returns a validation error from MintAPI
- verify the required parameters for that tool
- for channel-based YouTube tools, provide at least one stable identifier such as
idorforUsername - for Twitter/X pagination tools, reuse the returned
cursorexactly as provided
Package installs but plugin does not appear
- restart the OpenClaw gateway
- run
openclaw plugins inspect mintapi --runtime --json - verify the plugin is enabled
Link a local checkout into OpenClaw:
openclaw plugins install --link ./
openclaw plugins enable mintapi
openclaw plugins inspect mintapi --runtime --jsonRun checks locally:
npm test
npm run check
npm run pack:dry-run