I'm building a "web api" (I want to avoid the use of the term "REST" service). So I have two WebApi solutions, mine and yours! It can cause confusion, but that's my fault.
Now you can call your (excellent) web stack what you want, but I have some suggestions...
#1 "WCF" is a turn-off for those who were burned by the complexity of SOAP WCF.
#2 "Web API"... it's not really a web api in that its functionality isn't accessed over the web. Rather it's a set of assemblies that are accessed in-process. What it is is a Web API
If you want to consider a different name before you go live, maybe: Web Api Builder. The WAB. Microsoft WAB.
Just thinking out loud.