Verify a Marketing AI Tool Profile
Tool profile should show what evidence supports each capability and what remains untested.
Tool directory becomes useful when every record shows evidence state. Logo, tagline, and feature list copied from vendor page create marketing inventory, not independent index.
Inputs
- Canonical product URL
- Official documentation
- Public pricing page
- Public API or integration documentation
- Maintainer and submitter affiliations
- Defined test task, when observed evidence is claimed
1. Define profile scope
State exact job profile helps evaluate. "AI marketing platform" is too broad. "Turns approved brief into editable email series" can be checked.
Define:
- Target user
- Marketing job
- Required input
- Expected output
- Human approval points
- Data access and action permissions
2. Record official claims
Official documentation supports vendor-documented status. It does not prove speed, quality, reliability, or superiority.
Store claim with source URL and verification date:
statement: Product exposes public API
source_type: official-documentation
status: vendor-documented
verified_at: 2026-08-10
3. Run bounded test
Observed result requires reproducible task:
- Fixed input
- Account tier
- Product or model version
- Date and region
- Expected success condition
- Raw output or trace
Do not turn one successful run into universal capability claim.
4. Build claim ledger
Use five visible states:
| State | Meaning |
|---|---|
| Official | Vendor or publisher documents it |
| Observed | Dated test produced result |
| Inferred | Evidence supports conclusion indirectly |
| Stale | Source or test needs refresh |
| Unknown | Evidence cannot answer question |
5. Review conflicts
Disclose contributor relationship: maker, employee, investor, partner, customer, affiliate, or none. Affiliated profiles use same fields and require unaffiliated review when practical.
Publish gate
Profile ships only when canonical URL, material claims, source types, verification dates, affiliation, and correction path are present.
Failure modes
- Vendor marketing copy presented as editorial conclusion
- Pricing without check date
- Integration logo treated as working integration
- Beta access presented as general availability
- Unpublished test result converted into ranking
- Maintainer-affiliated product receives featured placement