Add Xquik to Social Media APIs and repair warning rendering

[kriptoburak]

Summary

• Add Xquik to the Social Media and Messengers API directory.
• Link the current official API overview and describe its 126 documented REST operations, OpenAPI 3.1 contract, webhooks, and MCP server.
• Use a durable paid classification instead of a stale per-read price.
• Add the required independent-service and trademark disclosure.

Independent Repository Fix

Repair the malformed unofficial API warning so GitHub renders it as an alert. The same cleanup also fixes the requets typo and replaces unsupported dash typography in 2 email API price cells.

Validation

• README table structure assertions passed.
• The official Xquik documentation URL returns HTTP 200.
• git diff --check passed.
• The edited README contains no prohibited dash forms.

Disclosure: I work on Xquik.

Xquik is an independent third-party service. Not affiliated with X Corp. "Twitter" and "X" are trademarks of X Corp.

[kriptoburak]

Repair pushed in add2772.

The Xquik row now points to the current official API overview, uses the verified 126-operation description, and avoids a brittle per-read price claim. The exact independent-service disclosure is included.

As an independent repository fix, the unofficial API warning now uses valid GitHub alert syntax. I also corrected an existing requets typo and unsupported dash typography in the email API table.

README structure checks, the live documentation URL check, and git diff --check pass.

Xquik is an independent third-party service. Not affiliated with X Corp. "Twitter" and "X" are trademarks of X Corp.

[kriptoburak]

I consolidated the reviewed patch into signed commit bf30622 so the branch now has a single verified commit on the current base. The content is unchanged: it adds the current Xquik API entry and independently repairs the GitHub warning syntax, the requets typo, and 2 malformed price separators.\n\nFresh validation confirms the README table cells, disclosure, warning syntax, spelling repair, HTTP 200 documentation link, and git diff --check. GitHub reports the PR mergeable with a clean merge state.