RESEARCH NOTE 001
Vugola AI review
A public API, an MCP connector, and two documentation conflicts worth checking before you spend credits.
Research updated · Hands-on test date: pending · Score: not assigned
The evidence in 30 seconds
| Paid tiers | Starter / Creator / Pro — see the pricing breakdown below |
|---|---|
| Free allowance / card required | Not verified |
| Publishing destinations | Vendor documentation and MCP repository disagree; verify inside the connected account |
| API / MCP | Public documentation and repository confirmed |
| Independent rating | Withheld until hands-on evidence exists |
Three things to check before a paid trial
API and MCP availability is documented. That makes automation a plausible use case, but does not establish reliability or editing quality. The vendor-maintained MCP repository separates hosted OAuth access from the local API-key server.
Credit wording is inconsistent: the API reference states one credit per started source minute, yet its 600-second example quotes 150 credits. Capture the returned quote and the final balance change before using either rule in a budget.
Publishing coverage is also inconsistent. The API introduction includes Instagram and Facebook; the repository says those destinations are temporarily unavailable and lists other destinations. Treat account-level availability as unresolved.
How to connect Vugola to your agent workflow
- Use the hosted MCP endpoint
https://www.vugolaai.com/api/mcpwith the client’s OAuth connection flow. The repository documents paid-plan access. - For a direct REST integration, store the API key server-side. The documented prefix is
vug_sk_; never place a real key in browser code or a public log. - Read account status, confirm available credits, and submit one rights-cleared source. Save the quote and job identifier.
- Wait for completion, retrieve exports, and inspect every accepted clip before permitting publishing. Keep the first test disconnected from automatic posting.
This is an integration plan based on public documentation, not a successful connection claim.
What we will measure
Use the shared three-source protocol. Record output count, accepted count, elapsed time, net credit charge, export properties, and repair minutes. Each source runs twice. No result values are available yet.
Potential strengths and unresolved limitations
Documented strengths
- Public integration documentation.
- Hosted OAuth route for agents.
- Plan-level credit allowances are published.
Concrete uncertainties
- Credit example conflicts with the stated rate.
- Publishing availability differs between sources.
- No independent quality or reliability evidence yet.
Pricing and credits
| Monthly plan | USD/month | Included credits | USD/credit* |
|---|---|---|---|
| Starter | 19.99 | 50 | 0.3998 |
| Creator | 49.99 | 300 | 0.1666 |
| Pro | 99.99 | 800 | 0.1250 |
*Our arithmetic: monthly price ÷ included credits, rounded. Assumes full utilization, excludes tax. Published prices, not measured output costs. Vendor pricing source ↗
A fair buying decision needs accepted outputs, not merely generated outputs. See our cost model before comparing subscriptions.
Frequently asked questions
Is Vugola AI free?
The checked pricing page lists paid plans. A usable free allowance and credit-card requirement have not been verified.
Does Vugola have an API?
Yes. Public API documentation exists. Access requires an active paid plan; API operation has not been tested by Scrutator.
Can I connect Vugola to an agent?
The public MCP repository documents a hosted OAuth connector. A documented connection is not proof of a successful end-to-end run.
Vugola vs Opus Clip: which is better?
We have no matched output evidence yet and do not declare a winner. Compare accepted clips and repair time on identical sources.