Hermes BibleUnofficial Docs
← All docs Docs / Core Features

X (Twitter) Search

X (Twitter) Search The tool lets the agent search X (Twitter) posts, profiles, and threads directly. It's backed by xAI's built in tool on the Responses API at

Core Features
Section
Core Features
Source
hermesbible.com/docs/user-guide/features/x-search

X (Twitter) Search The tool lets the agent search X (Twitter) posts, profiles, and threads directly. It's backed by xAI's built in tool on the Responses API at

Excerpt from the official Hermes Agent documentation, quoted for reference. View source

What this page covers

Section outline mirrored from the official Hermes Agent documentation. Follow any heading to read the complete text on the source site.

Upstream outline

  1. Authentication
  2. Enabling the tool
  3. Configuration
  4. Tool parameters
  5. Date validation
  6. Example
  7. Troubleshooting
  8. "No xAI credentials available"
  9. "x_search is not enabled for this model"
  10. Tool doesn't appear in the schema
  11. degraded: true — answer with no citations
  12. See Also

Section map

Authentication

Maps authentication to the Core Features documentation path, with the source page reserved for exact commands and updates.

Enabling the tool

Maps enabling the tool to the Core Features documentation path, with the source page reserved for exact commands and updates.

Configuration

Maps configuration to the Core Features documentation path, with the source page reserved for exact commands and updates.

Tool parameters

Maps tool parameters to the Core Features documentation path, with the source page reserved for exact commands and updates.

Date validation

Maps date validation to the Core Features documentation path, with the source page reserved for exact commands and updates.

Example

Maps example to the Core Features documentation path, with the source page reserved for exact commands and updates.

Troubleshooting

Maps troubleshooting to the Core Features documentation path, with the source page reserved for exact commands and updates.

"No xAI credentials available"

Maps "no xai credentials available" to the Core Features documentation path, with the source page reserved for exact commands and updates.

Implementation notes

  • Use this Core Features doc as a navigation page first: the local clone mirrors the source structure and links each heading back to the authoritative upstream section.
  • Primary decision areas: Authentication, Enabling the tool, Configuration, Tool parameters, Date validation. Read those source anchors before changing installs, credentials, automation, or runtime configuration.
  • Useful search signals for this doc: twitter, search, posts, profiles, threads. These are derived from the public title and summary so the clone remains lightweight.

Decision table

Best fitCore Features documentation

Use when you need orientation for x (twitter) search before applying exact upstream commands.

Verify firstAuthentication

Open the source anchor for Authentication and confirm platform-specific requirements before changing configuration.

Escalate to sourceCommands, credentials, runtime behavior

Use the upstream page as the authority for current syntax, release changes, and security-sensitive steps.

Verification checklist

  1. Use this page to orient yourself within Core Features, then open the linked source page for exact current syntax.
  2. Start with the source section for Authentication; do not rely on the local summary for commands or secrets.
  3. Check platform, install method, provider, and credential assumptions before changing a real environment.
  4. Review the source section for Enabling the tool if the page involves setup, automation, messaging, or runtime behavior.
  5. After applying anything from the source, run the smallest relevant smoke test before widening scope.

Risk notes

Credentials

Treat every token, OAuth grant, secret manager entry, and API key as production-sensitive. Verify least privilege and revocation before reuse.

External messages

Keep human review before sending public posts, customer messages, trading instructions, or team notifications.

Model spend

Set provider, token, and retry limits before scaling the workflow beyond a single test run.

Runtime access

Check filesystem, shell, browser, repository, and server permissions before granting the agent write access.

What this page covers

  • Core concept and where it fits in the Hermes Agent system.
  • Setup or operating context implied by the upstream page summary.
  • The source page link for full current details and updates.

Source mirror note

This page is generated from the public Hermes Bible index so the clone has the same route coverage and search surface. It stores the public title, category, summary, and source link locally; use the source page for full upstream text and updates.

Open source page