Mainly for standardizing the APIs I write myself, and also to help LLMs understand my APIs better. 1. Domain Use a dedicated domain whenever possible, for example api.example.com. 2. Path Always use lowercase letters. Do not include an /api prefix. Do not include file extensions. Do not put / at the end.

Because pricing and limits change over time, this article is only a reference for the time it was written. 1. Terminology RPM (requests per minute) Requests per minute RPD (requests per day) Requests per day TPM (tokens per minute) Tokens per minute TPD (tokens per day), Tokens per day

1. Choosing a Communication Protocol Ops systems are better suited to HTTP than to gRPC. More ops and R&D engineers are familiar with HTTP than with other protocols. Once you know the HTTP protocol, learning a RESTful-style HTTP API is quick. Being familiar to more people and easier to learn means better communication and lower handover cost, because they share more common domain background.

1. RESTful Requests 1 curl -X POST --data 'keyword=value' http://domain.com/mypath/ After -X you can also use DELETE, PUT, and so on. 2. Adding Headers 1 curl -H 'Content-Type:application/json' -H 'Authorization: bearer MyToken' http://domain.com/mypath/ 3. Basic Authentication 1 curl -u username:password http://domain.com/mypath/ 4. Download and Execute 1 curl -sSL http://domain.com/my.sh | bash 5.

1. Objects in Kubernetes Kubernetes objects are persistent entities in the system, used to represent the state of the cluster. Users interact with Kubernetes by operating on objects, telling the system the workload they expect. Objects are manipulated through the Kubernetes API. Every Kubernetes object contains two nested object fields, Spec and Status.