I like it, at least more than Zapier and similar pipelines. We have a couple of clients that use our API (geocoding[1]) to enrich their records inside an ETL. Be prepared that some APIs are rate-limited or quota-based, need API keys or other authentication and might return 'over-quota' error messages, never mind latency.
I just saw that the Geocoder API is free with certain limitations. If I find some free time, I would like to create an enricher for it. Maybe it can help your clients (and other people of course) to save some time :)
Say that during enrichment I might want to do some lookups what if one of them is not working...