PulseAugur
EN
LIVE 21:57:42

Goose users hit 404 errors with Perplexity due to incorrect API endpoint

By PulseAugur Editorial · [1 sources] ·

A technical issue has been identified with Goose's built-in Perplexity provider, causing a 404 error for users attempting to chat. The problem stems from an incorrect URL in the preset, which incorrectly appends '/v1' to the Perplexity API endpoint. This leads requests to a non-existent path, resulting in the 'Resource not found' error. The solution involves manually configuring a custom OpenAI-compatible provider in Goose, specifying the correct base URL without '/v1' and using the existing Perplexity API key. AI

IMPACT Users of Goose and Perplexity may need to reconfigure their API settings to avoid 404 errors when using chat features.

RANK_REASON This is a technical troubleshooting guide for a specific software product (Goose) and its integration with a third-party API (Perplexity), not a new release or significant industry event.

Read on dev.to — LLM tag →

AI-generated summary · Google Gemini · from 1 sources. How we write summaries →

Goose users hit 404 errors with Perplexity due to incorrect API endpoint

How we ranked this

Signal score
9 / 100
Composite score across the factors below. Higher = stronger signal that this story matters right now.
Newsworthiness bucket
Tool
This is a technical troubleshooting guide for a specific software product (Goose) and its integration with a third-party API (Perplexity), not a new release or significant industry event.
Source corroboration
Single-source cluster
Only one publisher covered this so far. Single-source stories can still rank when the publisher is high-authority, but they lack cross-source corroboration.
Topics
product, infra
Editorial topic classification. Feeds into how the story surfaces on /topic/<slug> hub pages and into the per-entity coverage mix.
AI-industry relevance
High
Clearly on-topic for AI-industry coverage.
Story freshness
Breaking (< 6h)
Fresh story with cross-source coverage still developing. Ranking may shift as more sources report.

Full methodology in our editorial standards.

COVERAGE [1]

  1. dev.to — LLM tag TIER_1 English(EN) · MilkyWay008 ·

    Goose + Perplexity 404 on Every Chat: the /v1 Trap and the Fix

    <p>If you pick Goose's built-in Perplexity provider and every chat dies with <code>Request failed: Resource not found (404)</code>, it's not your API key and it's probably not Perplexity being flaky. The preset ships pointing at a URL that doesn't exist.</p> <h2> What actually ha…

RELATED ENTITIES

RELATED TOPICS