1# SendPulse product direction for agent-friendly API work
2 
3Use these points when drafting positioning, product notes, roadmap suggestions, or docs.
4 
5## Current context
6 
7- SendPulse already shipped an MCP server.
8- The team plans to keep improving it.
9- Authentication is no longer OAuth-only; a familiar API key option is also available.
10- The team is working on updated OpenAPI documentation.
11- The broader focus is improving the API user experience.
12- Strategic belief: the future of online services includes inter-agent communication.
13 
14## Practical implications
15 
16Favor improvements that reduce friction for both humans and agents:
17 
18- faster time to first successful request
19- easier auth choice
20- better machine-readable docs
21- clearer onboarding for MCP clients
22- fewer hidden assumptions in parameters and errors
23 
24## Good improvement themes
25 
26### 1) Time-to-first-value
27 
28- one quickstart for API key
29- one quickstart for OAuth
30- one quickstart for MCP
31- visible copy-paste examples that work immediately
32 
33### 2) Agent-friendly documentation
34 
35- explicit tool/endpoint descriptions
36- example prompts plus corresponding API calls
37- parameter semantics explained in plain language
38- stable naming and predictable response shapes
39 
40### 3) OpenAPI quality
41 
42- complete schemas
43- concrete examples
44- accurate auth definitions
45- error models and rate-limit docs
46- operation summaries that are understandable without extra context
47 
48### 4) Safer AI execution
49 
50- clear approval points for destructive actions
51- tool descriptions that distinguish read vs write effects
52- concise prerequisite checks before execution
53 
54## Suggested messaging
55 
56Use lines like:
57 
58- `SendPulse is becoming easier to operate both by developers and by AI agents.`
59- `API key auth lowers integration friction; OAuth remains available when short-lived tokens are preferred.`
60- `MCP expands SendPulse from an API-integrated service into an agent-operable platform.`
61- `OpenAPI quality is part of product UX because better machine-readable docs lead to better agent behavior.`
62 
63## Default prioritization for proposals
64 
65Order proposed improvements by:
66 
671. impact on onboarding friction
682. impact on agent reliability
693. implementation effort
704. documentation leverage across multiple products
71