emohaa free api

Emohaa AI Free Service

Supports high-speed streaming output, multi-round dialogue, zero-configuration deployment, multi-channel token support, and automatic cleaning of session traces.

Fully compatible with ChatGPT interface.

There are also the following seven free-api welcome to pay attention to:

Moonshot AI (Kimi.ai) interface to API kimi-free-api

StepChat interface to API step-free-api

Alibaba Tongyi (Qwen) interface to API qwen-free-api

Zhipu AI (Zhipu Qingyan) interface to API glm-free-api

Metaso AI (Metaso) interface to API metaso-free-api

iFlytek Spark interface to API spark-free-api

MiniMax (Conch AI) interface to API hailuo-free-api

Table of contents

• Disclaimer
• Online experience
• Access preparation
  • Multiple account access
• Docker deployment
  • Docker-compose deployment
• Render deployment
• Vercel deployment
• Native deployment
• It is recommended to use the client
• interface list
  • Dialogue completion
  • Token survival detection
• Things to note
  • Nginx anti-generation optimization
  • Token statistics

Disclaimer

The reverse API is unstable. It is recommended to go to the official website of Lingxin Intelligence https://www.ai-beings.com/ to pay to use the API to avoid the risk of being banned.

This organization and individuals do not accept any financial donations or transactions. This project is purely for research, exchange and learning!

It is for personal use only, and it is prohibited to provide external services or commercial use to avoid putting pressure on the official service, otherwise it is at your own risk!

It is for personal use only, and it is prohibited to provide external services or commercial use to avoid putting pressure on the official service, otherwise it is at your own risk!

It is for personal use only, and it is prohibited to provide external services or commercial use to avoid putting pressure on the official service, otherwise it is at your own risk!

Online experience

This link is only a temporary test function and cannot be used for a long time. Please deploy it yourself for long-term use.

https://udify.app/chat/LDgsbVTfyTQ000Oq

Access preparation

Get token from echo.turing-world.com

Log in. Since emohaa disables the F12 developer tools, please install the Manage LocalStorage plug-in first, then open the plug-in on the current page and click the Export button to find Token value. This will be used as the Bearer Token value of Authorization: Authorization: Bearer TOKEN

Multiple account access

You can provide tokens for multiple accounts , use them together to provide:

Authorization: Bearer TOKEN1,TOKEN2,TOKEN3

One of these will be selected each time the service is requested.

Docker deployment

Please prepare a server with a public IP and open port 8000.

Pull the image and start the service

docker run -it -d --init --name emohaa-free-api -p 8000:8000 -e TZ=Asia/Shanghai vinlic/emohaa-free-api:latest

View real-time service logs

docker logs -f emohaa-free-api

Restart service

docker restart emohaa-free-api

Stop service

docker stop emohaa-free-api

Docker-compose deployment

 version : ' 3 '

services :
  emohaa-free-api :
    container_name : emohaa-free-api
    image : vinlic/emohaa-free-api:latest
    restart : always
    ports :
      - " 8000:8000 "
    environment :
      - TZ=Asia/Shanghai

Render deployment

Note: Some deployment areas may not be able to connect to emohaa. If the container log shows a request timeout or cannot be connected, please switch to other areas for deployment! Note: The container instance of the free account will automatically stop running after a period of inactivity, which will cause a delay of 50 seconds or more on the next request. It is recommended to check Render container keep alive

1. Fork this project to your github account.

2. Visit Render and log in to your github account.

3. Build your Web Service (New+ -> Build and deploy from a Git repository -> Connect your forked project -> Select the deployment area -> Select the instance type as Free -> Create Web Service).

4. After waiting for the construction to complete, copy the assigned domain name and splice the URL for access.

Vercel deployment

Note: The request response timeout for Vercel free accounts is 10 seconds, but the interface response usually takes longer, and you may encounter a 504 timeout error returned by Vercel!

Please make sure you have installed the Node.js environment first.

npm i -g vercel --registry http://registry.npmmirror.com
vercel login
git clone https://github.com/LLM-Red-Team/emohaa-free-api
cd emohaa-free-api
vercel --prod

Native deployment

Please prepare a server with a public IP and open port 8000.

Please install the Node.js environment and configure the environment variables first, and confirm that the node command is available.

Install dependencies

npm i

Install PM2 for process guarding

npm i -g pm2

Compile and build. When you see the dist directory, the build is complete.

npm run build

Start service

pm2 start dist/index.js --name " emohaa-free-api "

View real-time service logs

pm2 logs emohaa-free-api

Restart service

pm2 reload emohaa-free-api

Stop service

pm2 stop emohaa-free-api

It is recommended to use the client

It is faster and easier to use the following secondary development client to access the free-api series projects, and supports document/image upload!

LobeChat developed by Clivia https://github.com/Yanyutin753/lobe-chat

ChatGPT Web https://github.com/SuYxh/chatgpt-web-sea developed by Guangguang@

interface list

Currently, the /v1/chat/completions interface that is compatible with openai is supported. You can use the client access interface that is compatible with openai or other clients, or use online services such as dify to access it.

Dialogue completion

Conversation completion interface, compatible with openai's chat-completions-api.

POST /v1/chat/completions

header needs to set the Authorization header:

 Authorization: Bearer [refresh_token]

Request data:

{
    "messages" : [
        {
            "role" : " user " ,
            "content" : "你好"
        }
    ],
    // 如果使用SSE流请设置为true，默认false
    "stream" : false
}

Response data:

{
    "id" : " f73f02e6-6b43-4a46-ac24-3a9ea8d15145 " ,
    "model" : " emohaa " ,
    "object" : " chat.completion " ,
    "choices" : [
        {
            "index" : 0 ,
            "message" : {
                "role" : " assistant " ,
                "content" : " 你好啊！我是Emohaa，想和我聊点什么吗？ 今天心情如何？ "
            },
            "finish_reason" : " stop "
        }
    ],
    "usage" : {
        "prompt_tokens" : 1 ,
        "completion_tokens" : 1 ,
        "total_tokens" : 2
    },
    "created" : 1710603111
}

Token survival detection

Check whether the token is alive. If alive is not true, otherwise it is false. Please do not call this interface frequently (less than 10 minutes).

POST /token/check

Request data:

{
    "token" : " eyJhbGciOiJIUzUxMiIsInR5cCI6IkpXVCJ9... "
}

Response data:

{
    "live" : true
}

Things to note

Nginx anti-generation optimization

If you are using Nginx reverse proxy kimi-free-api, please add the following configuration items to optimize the output effect of the stream and optimize the experience.

 # 关闭代理缓冲。当设置为off时，Nginx会立即将客户端请求发送到后端服务器，并立即将从后端服务器接收到的响应发送回客户端。
proxy_buffering off ;
# 启用分块传输编码。分块传输编码允许服务器为动态生成的内容分块发送数据，而不需要预先知道内容的大小。
chunked_transfer_encoding on ;
# 开启TCP_NOPUSH，这告诉Nginx在数据包发送到客户端之前，尽可能地发送数据。这通常在sendfile使用时配合使用，可以提高网络效率。
tcp_nopush on ;
# 开启TCP_NODELAY，这告诉Nginx不延迟发送数据，立即发送小数据包。在某些情况下，这可以减少网络的延迟。
tcp_nodelay on ;
# 设置保持连接的超时时间，这里设置为120秒。如果在这段时间内，客户端和服务器之间没有进一步的通信，连接将被关闭。
keepalive_timeout 120 ;

Token statistics

Since the inference side no longer has kimi-free-api, the token cannot be counted and will be returned as a fixed number.