Can I pause a PumpGTM sequence through the API?

Yes. PATCH /sequences/{id}/status takes a required status field to pause or resume an existing sequence. To change its steps instead, PUT /sequences/{id} replaces them as a new revision and requires the expectedRevision you last read.

What are the rate limits for the PumpGTM API?

The OpenAPI spec does not state request rate limits. It does expose LinkedIn sending limits per account: GET /linkedin/accounts/{accountId}/sending-limits reads the daily invite cap and warm-up state, and the matching PATCH changes them. Check PumpGTM's developer documentation for API request limits.

How do I add leads to a PumpGTM sequence through Jentic?

Install Jentic One, import the PumpGTM API from the Jentic API Directory, and store your workspace key. Your agent searches for 'add people to an outreach sequence', Jentic returns POST /sequences/{id}/leads with its schema, and the agent calls it with the sequence id. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Is there a PumpGTM MCP server?

You don't need an MCP server to give your agent PumpGTM. Jentic connects it directly from the API Directory: import it, store your credential once, and your agent calls it, discovering operations on demand rather than loading every tool definition into its context.

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

Yes. For example, write a rule that allows GET /replies, POST /replies/{id}/decide, and GET /sequences/{id} only for sequence 'seq_123', so the agent can triage replies and read that one sequence but cannot create sequences, perform X actions, or delete webhooks. Every call it makes is logged.

Can the PumpGTM API act on X as my connected account?

Yes. POST /x/actions follows, likes, or reposts as a connected account, taking a required action and target. GET /x/accounts lists the connected X identities, and POST /x/eligibility checks whether a set of leads follows a given account.