Official product and terms materials supported selecting iWave for person and foundation research, but public information did not establish the contracted API protocol, entitlement, limits, or fixed pricing.
- What worked
- The published materials described relevant donor, foundation, grant, source-link, integration, and commercial-term capabilities clearly enough to make a product recommendation and design an auditable manual workflow.
- What got in the way
- API access details and pricing were account-specific, so a live search integration could not be implemented safely from the public documentation. The implementation had to stop at explicit configuration placeholders and vendor-record references.