docs(community): add Future AGI integration page

[SuhaniNagpal7]

Summary

Adds a community integration page at src/content/docs/community/integrations/future-agi.mdx documenting how to send Strands agent traces to Future AGI — an open-source e2e agent engineering and optimization platform that helps you ship self-improving AI agents.

The page mirrors the structure of the existing ag-ui.mdx community integration page (frontmatter, tone, length).

What changed

• New file: src/content/docs/community/integrations/future-agi.mdx
• Two setup paths covered:
  1. Recommended: traceai-strands + fi_instrumentation.register() + configure_strands_tracing() — handles the project resource attributes Future AGI uses for dashboard bucketing.
  2. Manual: Strands' built-in StrandsTelemetry().setup_otlp_exporter() plus OTEL_EXPORTER_OTLP_ENDPOINT / OTEL_EXPORTER_OTLP_HEADERS / OTEL_RESOURCE_ATTRIBUTES env vars.

Smoke test

Verified end-to-end against the Future AGI tracer endpoint:

• POST https://api.futureagi.com/tracer/v1/traces with x-api-key + x-secret-key → HTTP 200 OK.
• A test span carrying project_name, project_type=observe, project_version_name=DEFAULT, and project_version_id resource attributes surfaced in the Future AGI dashboard under the named project. Spans without those attributes are accepted but land in the unnamed bucket — this is why the page leads with the traceai-strands path.

Relationship to #809

This is a separate, additive PR. #809 adds a single bullet to the visualization-options list in traces.mdx. This PR adds the fuller community-integration page. Either or both can be merged independently.

Test plan

• Astro / mkdocs build passes
• Maintainer happy with placement under community/integrations/ (matches ag-ui.mdx)
• Confirm wording on the resource-attribute caveat is acceptable

🤖 Generated with Claude Code

[zastrowm]

you'll also need to update the nav to have this visible from the sidebar

[github-actions]

Issue: The standard OpenTelemetry convention is that OTEL_EXPORTER_OTLP_ENDPOINT should be a base URL (the SDK appends /v1/traces automatically), while OTEL_EXPORTER_OTLP_TRACES_ENDPOINT is the signal-specific variant that takes the full path.

Here you're using OTEL_EXPORTER_OTLP_ENDPOINT with the full /v1/traces path, which would typically result in the SDK posting to https://api.futureagi.com/tracer/v1/traces/v1/traces.

This is consistent with how other pages in this docs repo handle it — see agentcore_evaluation_dashboard.mdx which uses OTEL_EXPORTER_OTLP_TRACES_ENDPOINT for full-path endpoints.

Suggestion: Either use:

export OTEL_EXPORTER_OTLP_TRACES_ENDPOINT="https://api.futureagi.com/tracer/v1/traces"

or:

export OTEL_EXPORTER_OTLP_ENDPOINT="https://api.futureagi.com/tracer"

Please verify which approach works with your smoke test — it's possible Strands' setup_otlp_exporter() handles this differently, but it should be documented correctly to avoid user confusion.

[github-actions]

Issue: The navigation sidebar hasn't been updated to include this new page.

As zastrowm already noted, you'll need to add the page to src/config/navigation.yml under the Community > Integrations section:

      - label: Integrations
        items:
          - docs/community/integrations/ag-ui
          - docs/community/integrations/future-agi

[github-actions]

Issue: The description says Future AGI is "open-source" but there's no link to a source repository. The links point to futureagi.com (a commercial product) and the PyPI package traceai-strands.

Suggestion: If Future AGI is open-source, add a link to the source repository. If it's a commercial platform with open-source integration packages, consider rewording to something like "Future AGI is an e2e agent engineering and optimization platform..." to avoid confusion.

[github-actions]

Issue: These environment variables are used in the code example below (Option 1) implicitly via register(), but the relationship isn't clear. The register() call presumably reads FI_API_KEY and FI_SECRET_KEY from the environment, but this isn't explicitly stated.

Suggestion: Add a brief note like "These are read automatically by the fi_instrumentation library." to make the connection explicit for users.

[github-actions]

Minor: The fi_instrumentation package dependency isn't explicitly listed in the install command. Is it installed as a dependency of traceai-strands, or does it need to be installed separately?

If it's a transitive dependency, this is fine. If not, the install command should include it:

pip install 'strands-agents[otel]' traceai-strands fi-instrumentation

[github-actions]

Assessment: Request Changes

The page is well-structured and follows the existing ag-ui.mdx pattern. Two items need addressing before merge:

Review Categories

• Navigation: The page won't be visible without adding it to src/config/navigation.yml (as already noted by zastrowm)
• Technical accuracy: The OTEL_EXPORTER_OTLP_ENDPOINT usage with a full /v1/traces path is inconsistent with OpenTelemetry conventions and other pages in this repo — likely should be OTEL_EXPORTER_OTLP_TRACES_ENDPOINT instead
• Clarity: Minor gaps in explaining the connection between prerequisites (env vars) and the code that uses them, and the "open-source" claim needs substantiation

Good addition to the community integrations section — the dual-path approach (recommended package vs manual OTLP) is a nice pattern for users with different dependency preferences.

[github-actions]

Documentation Preview Ready

Your documentation preview has been successfully deployed!

Preview URL: https://d3ehv1nix5p99z.cloudfront.net/pr-cms-810/docs/user-guide/quickstart/overview/

Updated at: 2026-05-13T18:32:34.517Z