Evaluating RedFox and a self-hosted API
Evaluating RedFox and a self-hosted API. Follow concrete contracts, examples and reviewable steps using Xiaohongshu (RedNote), Douyin, WeChat Official Accounts.
Copy the agent prompt manually
Define verifiable requirements
This is a framework for evaluating buying versus building, not a live competitor benchmark. Third-party prices, reliability, authorization and reviews have not been verified, and local fixtures cannot replace real-provider tests.
Compare the same task
| Dimension | DataNavoAPI local implementation | Evidence to request elsewhere |
|---|---|---|
| API | 237 capability contracts with local simulation | Inputs, fields, conditions and real samples |
| MCP | Local stdio / HTTP with explicit execution | Transport, authentication and client compatibility |
| Cost | TEST_CREDIT | Per-call/item rules, empty results, failures, pagination and retries |
| Operations | Local accounts, receipts and audit | Availability evidence, retention, exit and export options |
Bounded evaluation
- Use the same keywords, accounts or content identifiers and record observation times.
- Test success, empty results, missing fields, failures and replay.
- Estimate the requests needed for the whole task rather than isolated minimum unit prices.
Clear inputs. Inspectable output.
Each click runs a local fixture. Advanced JSON inputs are checked against the selected method. Editing does not execute a request.
Copying does not execute. CLI quote is read-only and needs a local customer TEST key. Configure MCP in demo mode first. GET and POST batches both return only fictional local fixtures.
Download contract example (no execution) ↗For TEST budgets, Key scopes or failure scenarios, open the account console. Customer sandbox ↗