Analyse the endpoins for processes, decisions, rules and other services and check the consistency like, naming convention, attributes on queries, paths, headers, used HTTP methods, response codes...

Based on the analyse result, propose a guideline that could be used to keep consistency on all the exposed APIs. This may be extended even to messaging APIs, topics, and Events.

It is important that APIs are consistent before the 1.0 once the public APIs are published and being used it is difficult to change them because it breaks all clients using them.

One idea it regarding metada related to resources, how can we use it where the client may associate any kind of metadata ( corellation ids, labels, etc).