Not really sure how to phrase this question and can't quite discern what the intended behaviour is from the documentation, but here goes.

I have a minimal file structure in the app directory as follows

-app
  -[...slug]
    -page.js
  -api
    -first
      -route.js
    -second
      -route.js
    -not-found.js
  -page.js
  -not-found.js

The behaviour seems to be that if I navigate to an API route that doesn't exist (e.g. /api/third) it will then render the page from [...slug]/page.js
Similarly this produces the same result

-app
  -[slug]
    -page.js
    -[...nestedSlug]
      -page.js
  -api
    -first
      -route.js
    -second
      -route.js
    -not-found.js
  -page.js
  -not-found.js

I would like to have it render one of the two "not-found" files instead, as I would have expected that the slug shouldn't cover the API route and should only be handling any undefined root-level nested routes
Is this something that's possible by restructuring my routes while keeping a top-level catch-all for non-API routes?